Information exchange for network coordination of ue-to-ue cross-link interference measurement

ABSTRACT

In NR networks with dynamic TDD operation, two types of cross-link interference (CLI) arise: UE-to-UE and TRP-to-TRP. UE-to-UE CLI measurement and reporting can assist the network in managing CLI. The problem is that, for a cell to be able to measure the CLI reference signal transmitted by UEs in another neighboring cell, the cell needs to know what CLI-RS transmission resources assigned to the UEs in the neighboring cells. Embodiments of the present disclosure provide systems and methods for the exchange of such information between cells. In some embodiments, for example, a gNB sends a request message to a neighboring gNB and the neighboring gNB sends back a response message that includes TDD DL/UL Configurations of its cells and a list of the resources assigned to its UEs for transmission of UE-to-UE CLI reference signal.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of U.S. Provisional PatentAppl. No. 62/791,567, filed Jan. 11, 2019, which is incorporated hereinby reference in its entirety.

BACKGROUND

Various embodiments generally may relate to the field of wirelesscommunications.

SUMMARY

Some embodiments can include a first access node for implementing across-link interference (CLI) information exchange procedure in awireless communication system. The first access node can include radiofront end circuitry and processor circuitry. The radio front endcircuitry can receive a CLI request signal from a second access node.The processor circuitry can generate a CLI response signal, where theCLI response signal includes time-division duplex (TDD) configurationinformation. The radio front end circuitry can transmit the CLI responsesignal to the second access node.

In these embodiments, the TDD configuration information can include alist of TDD configurations. The list of TDD configurations can include acell identifier (ID), or a common TDD configuration.

In these embodiments, the TDD configuration can include a list ofdedicated TDD configurations. The list of dedicated TDD configurationscan include a dedicated TDD configuration, or a user equipment (UE)identifier (ID).

In these embodiments, the TDD configuration information can include alist of user equipment (UE) CLI reference signal (RS) transmissionconfigurations. The list of UE CLI RS transmission configurations caninclude a UE CLI RS transmission configuration, or a UE identifier (ID).

In these embodiments, the radio front end circuitry can receive the CLIrequest signal and can transmit the CLI response signal over an Xninterface or a F1 interface.

Some embodiments can include a first access node for implementing across-link interference (CLI) information exchange procedure in awireless communication system. The first access node can include radiofront end circuitry and processor circuitry. The processor circuitry cangenerate a CLI request signal. The radio front end circuitry cantransmit the CLI request signal to a second access node, and can receivea CLI response signal from the second access node, the CLI responsesignal including time-division duplex (TDD) configuration information.

In these embodiments, the TDD configuration information can include alist of TDD configurations. The list of TDD configurations can include acell identifier (ID), or a common TDD configuration.

In these embodiments, the TDD configuration can include a list ofdedicated TDD configurations. The list of dedicated TDD configurationscan include a dedicated TDD configuration, or a user equipment (UE)identifier (ID).

In these embodiments, the TDD configuration information can include alist of user equipment (UE) CLI reference signal (RS) transmissionconfigurations. The list of UE CLI RS transmission configurations caninclude a UE CLI RS transmission configuration, or a UE identifier (ID).

In these embodiments, the radio front end circuitry can receive the CLIrequest signal and can transmit the CLI response signal over an Xninterface or a F1 interface.

Some embodiments can include a system for implementing a cross-linkinterference (CLI) information exchange procedure in a wirelesscommunication system. The system includes a first access node and asecond access node. The first can generate a CLI request signal. Thesecond access node can receive the CLI request signal from the firstaccess node, and can generate a CLI response signal, the CLI responsesignal including time-division duplex (TDD) configuration information.The first access node can receive the CLI response signal from thesecond access node.

In these embodiments, the TDD configuration information can include alist of TDD configurations, a list of dedicated TDD configurations, or alist of user equipment (UE) CLI reference signal (RS) transmissionconfigurations.

In these embodiments, the first access node can receive the CLI responsesignal and the second access node can receive the CLI request signalover an Xn interface or a F1 interface.

Some embodiments include a method performed by a first access node forimplementing a cross-link interference (CLI) information exchangeprocedure in a wireless communication system. The method includingreceiving a CLI request signal from a second access node, generating aCLI response signal, the CLI response signal including time-divisionduplex (TDD) configuration information, and transmitting the CLIresponse signal to the second access node. The TDD configurationinformation can be implemented for wireless communication at the firstaccess node and/or second access node.

Some embodiments include a method performed by a first access node forimplementing a cross-link interference (CLI) information exchangeprocedure in a wireless communication system according to embodiments ofthe disclosure. The method includes generating a CLI request signal atthe first access node and transmitting the CLI request signal to asecond access node, The method further includes receiving a CLI responsesignal from the second access node, the CLI response signal includingtime-division duplex (TDD) configuration information. The TDDconfiguration information can be implemented for wireless communicationat the first access node and/or second access node.

Any of the above-described embodiments may be combined with any otherembodiments (or combination of embodiments), unless explicitly statedotherwise. The foregoing description of one or more implementationsprovides illustration and description, but is not intended to beexhaustive or to limit the scope of embodiments to the precise formdisclosed. Modifications and variations are possible in light of theabove teachings or may be acquired from practice of various embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS/FIGURES

The present disclosure is described with reference to the accompanyingdrawings. In the drawings, like reference numbers indicate identical orfunctionally similar elements. Additionally, the left most digit(s) of areference number identifies the drawing in which the reference numberfirst appears. In the accompanying drawings:

FIG. 1 graphically illustrates two types of cross-link interference(CLI) network in accordance with various embodiments;

FIG. 2 graphically illustrates a CLI information exchange procedure inaccordance with various embodiments;

FIG. 3 illustrates exemplary architecture of a system of a network inaccordance with various embodiments;

FIG. 4 illustrates an example architecture of a system including a firstCN in accordance with various embodiments;

FIG. 5 illustrates an architecture of a system including a second CN inaccordance with various embodiments;

FIG. 6 illustrates an example of infrastructure equipment in accordancewith various embodiments;

FIG. 7 illustrates an example of a platform (or “device”) in accordancewith various embodiments;

FIG. 8 illustrates example components of baseband circuitry and radiofront end modules (RFEMs) in accordance with various embodiments;

FIG. 9 illustrates various protocol functions that can be implemented ina wireless communication device in accordance with various embodiments;

FIG. 10 illustrates components of a core network in accordance withvarious embodiments;

FIG. 11 is a block diagram illustrating components, according to someexample embodiments, of a system to support Network FunctionsVirtualization (NFV); and

FIG. 12 is a block diagram illustrating components, according to someexample embodiments, able to read instructions from a machine-readableor computer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein.

FIG. 13 illustrates a first flowchart for implementing a cross-linkinterference (CLI) information exchange procedure in a wirelesscommunication system.

FIG. 14 illustrates a second flowchart for implementing a cross-linkinterference (CLI) information exchange procedure in a wirelesscommunication system.

The present disclosure will now be described with reference to theaccompanying drawings.

DETAILED DESCRIPTION OF THE DISCLOSURE

The following detailed description refers to the accompanying drawings.The same reference numbers may be used in different drawings to identifythe same or similar elements. In the following description, for purposesof explanation and not limitation, specific details are set forth suchas particular structures, architectures, interfaces, techniques, etc. inorder to provide a thorough understanding of the various aspects ofvarious embodiments. However, it will be apparent to those skilled inthe art having the benefit of the present disclosure that the variousaspects of the various embodiments may be practiced in other examplesthat depart from these specific details. In certain instances,descriptions of well-known devices, circuits, and methods are omitted soas not to obscure the description of the various embodiments withunnecessary detail. For the purposes of the present document, the phrase“A or B” means (A), (B), or (A and B).

Overview

In NR networks with dynamic TDD operation, two types of cross-linkinterference (CLI) arise: UE-to-UE and TRP-to-TRP. UE-to-UE CLImeasurement and reporting can assist the network in managing CLI. Theproblem is that, for a cell to be able to measure the CLI referencesignal transmitted by UEs in another neighboring cell, the cell needs toknow what CLI-RS transmission resources assigned to the UEs in theneighboring cells. Embodiments of the present disclosure provide systemsand methods for the exchange of such information between cells. In someembodiments, for example, a gNB sends a request message to a neighboringgNB and the neighboring gNB sends back a response message that includesTDD DL/UL Configurations of its cells and a list of the resourcesassigned to its UEs for transmission of UE-to-UE CLI reference signal.

Exemplary Cross-Link Interference (CLI)

FIG. 1 graphically illustrates two types of cross-link interference(CLI) network in accordance with various embodiments. As illustrated inFIG. 1, two types of cross-link interference (CLI) arise under dynamicTDD operation, namely, UE-to-UE interference and TRP-to-TRPinterference, in NR, where TRP is transmission reception point. In theexemplary embodiment illustrated in FIG. 1, a UE-to-UE reference signalfor CLI (CLI-RS) is considered to be introduced in NR Rel-16 to enablemeasurement of UE-to-UE CLI. Each cell configures its UEs with resourcesfor CLI-RS transmission and CLI-RS measurements. To enable coordinationof transmission and measurements of CLI-RS, information exchange betweengNBs can be beneficial.

In some embodiments, for L3 measurement, DL/UL configurations in eachcell can be exchanged, so that UEs in one cell would not attempt tomeasure CLI from neighboring UEs that are actually not transmitting anysignals because their cell is in DL transmission. In addition, gNBs cancoordinate with each other on CLI-RS configurations (e.g.,time/frequency resource mapping, sequence index, periodicity, etc.) sothat UEs can be informed with neighboring cell's CLI-RS configurationfor CLI measurement. Embodiments of the present disclosure help providefor the exchange of such information between gNBs.

FIG. 2 graphically illustrates a CLI information exchange procedure inaccordance with various embodiments. As illustrated in FIG. 2, the gNB1initiates the procedure by sending the CLI INFORMATION REQUEST messageto gNB2. The candidate NG-RAN node₂ replies with the CLI RESPONSEmessage.

In some embodiments, the CLI INFORMATION REQUEST message can be sent bya gNB node to a neighboring gNB to request information for CLIcoordination. As illustrated in the table below, the CLI INFORMATIONREQUEST message can be characterized as including.

Information Element Presence Message Type Mandatory

In some embodiments, the CLI INFORMATION RESPONSE message can be sent bya gNB to a neighboring gNB node to provide information relevant toCLI-RS configurations. As illustrated in the table below, the CLIINFORMATION RESPONSE message can be characterized as including:

Information Element Presence Message Type Mandatory List of TDDConfiguration Mandatory >Cell ID Mandatory >Common TDD ConfigurationMandatory > List of Dedicated TDD Configurations Optional >>DedicatedTDD Configuration >>UE ID List of UE CLI RS Transmission ConfigurationOptional >UE CLI RS Transmission Configuration >UE ID

In some embodiments, the “Common TDD Configuration” from the above tablecan be TDD-UL-DL-ConfigCommon as defined in TS 38.331 and the “DedicatedTDD Configuration” from the above table can be TDD-UL-DL-ConfigDedicatedas defined in TS 38.331. In some embodiments, the “UE CLI RSTransmission Configuration” from the above table can be SRS-Configdefined in TS 38.331. The TDD-UL-DL-ConfigCommon,TDD-UL-DL-ConfigDedicated, SRS-Config and CLI-RS-TxResourceConfig areprovided below for convenience.

CLI-RS-TxResourceConfig information element CLI-RS-TxResourceConfig ::=SEQUENCE {   cli-RS-TxResourceConfigId CLI-RS-TxResourceConfigId,  cli-RS-TxResourceSetList SEQUENCE(SIZE(1..maxNrofCLI-RS-ResourcesSetPerConfig)) ofCLI-RS-TxResourceSetId,   bwp-Id       BWP-Id, } CLI-RS-TxResourceSet::= SEQUENCE {   cli-RS-TxResourceSetIdCLI-RS-TxResourceSetId,  cli-RS-TxResourceIdList SEQUENCE(SIZE(1..maxNrofCLI-RS-TxResourcesPerSet)) of CLI- RS-TxResourceId,OPTIONAL,   resourceType     CHOICE {    aperiodic,    semi-persistentSEQUENCE{     periodicityAndOffset   },   periodic       SEQUENCE{   periodicityAndOffset   }  }, OPTIONAL,  cli-RS-TxPowerControl,OPTIONAL, } TDD-UL-DL-Config information element TDD-UL-DL-ConfigCommon::= SEQUENCE {  referenceSubcarrierSpacing  SubcarrierSpacing,  pattern1 TDD-UL-DL-Pattern,  pattern2  TDD-UL-DL-Pattern     OPTIONAL, -- Need R ... } TDD-UL-DL-Pattern ::= SEQUENCE {  dl-UL-TransmissionPeriodicity ENUMERATED {ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10}, nrofDownlinkSlots  INTEGER (0..maxNrofSlots),  nrofDownlinkSymbols INTEGER (0..maxNrofSymbols-1),  nrofUplinkSlots  INTEGER(0..maxNrofSlots),  nrofUplinkSymbols  INTEGER (0..maxNrofSymbols-1), ... } TDD-UL-DL-ConfigDedicated ::= SEQUENCE { slotSpecificConfigurationsToAddModList  SEQUENCE (SIZE(1..maxNrofSlots)) OF TDD-UL-DL- SlotConfig    OPTIONAL, -- Need N slotSpecificConfigurationsToreleaseList   SEQUENCE (SIZE(1..maxNrofSlots)) OF TDD-UL-DL- SlotIndex     OPTIONAL, -- Need N  ...} TDD-UL-DL-SlotConfig ::= SEQUENCE {  slotIndex  TDD-UL-DL-SlotIndex, symbols  CHOICE {   allDownlink   NULL,   allUplink   NULL,   explicit  SEQUENCE {    nrofDownlinkSymbols    INTEGER (1..maxNrofSymbols-1)    OPTIONAL,  -- Need S    nrofUplinkSymbols    INTEGER(1..maxNrofSymbols-1)     OPTIONAL  -- Need S   }  } }TDD-UL-DL-SlotIndex ::= INTEGER (0..maxNrofSlots-1) TDD-UL-DL-Pattern::= SEQUENCE {  dl-UL-TransmissionPeriodicity  ENUMERATED {ms0p5,ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10},  nrofDownlinkSlots INTEGER (0..maxNrofSlots),  nrofDownlinkSymbols  INTEGER(0..maxNrofSymbols-1),  nrofUplinkSlots  INTEGER (0..maxNrofSlots), nrofUplinkSymbols  INTEGER (0..maxNrofSymbols-1),  ... } SRS-Configinformation element SRS-Config ::=  SEQUENCE { srs-ResourceSetToReleaseList   SEQUENCE(SIZE(1..maxNrofSRS-ResourceSets)) OF SRS- ResourceSetId  OPTIONAL, --Need N  srs-ResourceSetToAddModList   SEQUENCE(SIZE(1..maxNrofSRS-ResourceSets)) OF SRS- ResourceSet   OPTIONAL, --Need N  srs-ResourceToReleaseList   SEQUENCE(SIZE(1..maxNrofSRS-Resources)) OF SRS- ResourceId    OPTIONAL,  -- NeedN  srs-ResourceToAddModList   SEQUENCE (SIZE(1..maxNrofSRS-Resources))OF SRS- Resource     OPTIONAL,  -- Need N  tpc-Accumulation   ENUMERATED{disabled}    OPTIONAL,  -- Need S  ... } SRS-ResourceSet ::=  SEQUENCE{  srs-ResourceSetId   SRS-ResourceSetId,  srs-ResourceIdList   SEQUENCE(SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-ResourceId OPTIONAL, --Cond Setup  resourceType   CHOICE {   aperiodic    SEQUENCE {   aperiodicSRS-ResourceTrigger     INTEGER(1..maxNrofSRS-TriggerStates-1),    csi-RS     NZP-CSI-RS-ResourceId   OPTIONAL,  -- Cond NonCodebook    slotOffset     INTEGER (1..32)   OPTIONAL, -- Need S    ...   },   semi-persistent    SEQUENCE {   associatedCSI-RS     NZP-CSI-RS-ResourceId    OPTIONAL, -- CondNonCodebook    ...   },   periodic    SEQUENCE {    associatedCSI-RS    NZP-CSI-RS-ResourceId    OPTIONAL, -- Cond NonCodebook    ...   } },  usage   ENUMERATED {beamManagement, codebook, nonCodebook,antennaSwitching},  alpha   Alpha    OPTIONAL, -- Need S  p0   INTEGER(-202..24)    OPTIONAL, -- Cond Setup  pathlossReferenceRS   CHOICE {  ssb-Index    SSB-Index,   csi-RS-Index    NZP-CSI-RS-ResourceId  }   OPTIONAL, -- Need M  srs-PowerControlAdjustmentStates   ENUMERATED {sameAsFci2, separateClosedLoop}    OPTIONAL, -- Need S  ... }

Exemplary Systems

FIG. 3 illustrates exemplary architecture of a system of a network inaccordance with various embodiments. The following description isprovided for an example system 300 that operates in conjunction with theLong Term Evolution (LTE) system standards and Fifth Generation (5G) orNR system standards as provided by Third Generation Partnership Project(3GPP) technical specifications. However, the example embodiments arenot limited in this regard and the described embodiments may apply toother networks that benefit from the principles described herein, suchas future 3GPP systems (e.g., Sixth Generation (6G)) systems, IEEE802.16 protocols (e.g., WMAN, WiMAX, etc.), or the like.

As illustrated in FIG. 3, the system 300 includes User Equipment (UE)301 a and UE 301 b (collectively referred to as “UEs 301” or “UE 301”).In this example, UEs 301 are illustrated as smartphones (e.g., handheldtouchscreen mobile computing devices connectable to one or more cellularnetworks), but may also comprise any mobile or non-mobile computingdevice, such as consumer electronics devices, cellular phones,smartphones, feature phones, tablet computers, wearable computerdevices, personal digital assistants (PDAs), pagers, wireless handsets,desktop computers, laptop computers, in-vehicle infotainment (IVI),in-car entertainment (ICE) devices, an Instrument Cluster (IC), head-updisplay (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobileequipment (DME), mobile data terminals (MDTs), Electronic EngineManagement System (EEMS), electronic/engine control units (ECUs),electronic/engine control modules (ECMs), embedded systems,microcontrollers, control modules, engine management systems (EMS),networked or “smart” appliances, MTC devices, M2M, IoT devices, and/orthe like.

In some embodiments, any of the UEs 301 may be Internet of Things (IoT)UEs, which may comprise a network access layer designed for low-powerIoT applications utilizing short-lived UE connections. An IoT UE canutilize technologies such as Machine-to-Machine (M2M) or Machine-TypeCommunications (MTC) for exchanging data with an MTC server or devicevia a Public Land Mobile Network (PLMN), Proximity-Based Service(ProSe), or Device-to-Device (D2D) communication, sensor networks, orIoT networks. The M2M or MTC exchange of data may be a machine-initiatedexchange of data. An IoT network describes interconnecting IoT UEs,which can include uniquely identifiable embedded computing devices(within the Internet infrastructure), with short-lived connections. TheIoT UEs may execute background applications (e.g., keep-alive messages,status updates, etc.) to facilitate the connections of the IoT network.

The UEs 301 can be configured to connect, for example, communicativelycouple, with a Radio Access Network (RAN) 310. In some embodiments, theRAN 310 may be a Next Generation (NG) RAN or a 5G RAN, an evolvedUniversal Terrestrial Radio Access Network (E-UTRAN), or a legacy RAN,such as a UTRAN or GSM EDGE Radio Access Network (GERAN). As usedherein, the term “NG RAN,” or the like, may refer to a RAN 310 thatoperates in an NR or 5G system 300, and the term “E-UTRAN,” or the like,may refer to a RAN 310 that operates in an LTE or 4G system 300. The UEs301 utilize connections (or channels) 303 and 304, respectively, each ofwhich comprises a physical communications interface or layer (discussedin further detail below).

In this example, the connections 303 and 304 are illustrated as an airinterface to enable communicative coupling, and can be consistent withcellular communications protocols, such as a Global System for MobileCommunications (GSM) protocol, a Code-Division Multiple Access (CDMA)network protocol, a Push-to-Talk (PTT) protocol, a Push-to-Talk overCellular (POC) protocol, a Universal Mobile Telecommunications System(UMTS) protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol,and/or any of the other communications protocols discussed herein. Insome embodiments, the UEs 301 may directly exchange communication datavia a Proximity-Based Service (ProSe) interface 305. The ProSe interface305 may alternatively be referred to as a sidelink (SL) interface 305and may comprise one or more logical channels, including but not limitedto a Physical Sidelink Control Channel (PSCCH), a Physical SidelinkShared Channel (PSSCH), a Physical Sidelink Downlink Channel (PSDCH),and a Physical Sidelink Broadcast Channel (PSBCH).

The UE 301 b is shown to be configured to access an Access Point (AP)306 (also referred to as “WLAN node 306,” “WLAN 306,” “WLAN Termination306,” “WT 306” or the like) via connection 307. The connection 307 cancomprise a local wireless connection, such as a connection consistentwith any IEEE 802.11 protocol, wherein the AP 306 would comprise awireless fidelity (Wi-Fi®) router. In this example, the AP 306 is shownto be connected to the Internet without connecting to the core networkof the wireless system (described in further detail below). In variousembodiments, the UE 301 b, RAN 310, and AP 306 can be configured toutilize LWA operation and/or LWIP operation. The LWA operation mayinvolve the UE 301 b in RRC_CONNECTED being configured by a RAN node 311a-b to utilize radio resources of LTE and WLAN. LWIP operation mayinvolve the UE 301 b using WLAN radio resources (e.g., connection 307)via IPsec protocol tunneling to authenticate and encrypt packets (e.g.,IP packets) sent over the connection 307. IPsec tunneling can includeencapsulating the entirety of original IP packets and adding a newpacket header, thereby protecting the original header of the IP packets.

The RAN 310 can include one or more AN nodes or RAN nodes 311 a and 311b (collectively referred to as “RAN nodes 311” or “RAN node 311”) thatenable the connections 303 and 304. As used herein, the terms “accessnode,” “access point,” or the like may describe equipment that providesthe radio baseband functions for data and/or voice connectivity betweena network and one or more users. These access nodes can be referred toas BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs or TRPs, and so forth,and can comprise ground stations (e.g., terrestrial access points) orsatellite stations providing coverage within a geographic area (e.g., acell). As used herein, the term “NG RAN node” or the like may refer to aRAN node 311 that operates in an NR or 5G system 300 (for example, agNB), and the term “E-UTRAN node” or the like may refer to a RAN node311 that operates in an LTE or 4G system 300 (e.g., an eNB). Inaccordance with various embodiments, the RAN nodes 311 can beimplemented as one or more of a dedicated physical device such as amacrocell base station, and/or a low power (LP) base station forproviding femtocells, picocells or other like cells having smallercoverage areas, smaller user capacity, or higher bandwidth compared tomacrocells.

In some embodiments, all or parts of the RAN nodes 311 can beimplemented as one or more software entities running on server computersas part of a virtual network, which may be referred to as a CRAN and/ora virtual baseband unit pool (vBBUP). In these embodiments, the CRAN orvBBUP may implement a RAN function split, such as a PDCP split whereinRRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocolentities are operated by individual RAN nodes 311; a MAC/PHY splitwherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN/vBBUPand the PHY layer is operated by individual RAN nodes 311; or a “lowerPHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of thePHY layer are operated by the CRAN/vBBUP and lower portions of the PHYlayer are operated by individual RAN nodes 311. This virtualizedframework allows the freed-up processor cores of the RAN nodes 311 toperform other virtualized applications. In some embodiments, anindividual RAN node 311 may represent individual gNB-DUs that areconnected to a gNB-CU via individual F1 interfaces (not illustrated inFIG. 3). In these implementations, the gNB-DUs can include one or moreremote radio heads or RFEMs (see, for example, FIG. 6), and the gNB-CUmay be operated by a server that is located in the RAN 310 (not shown)or by a server pool in a similar manner as the CRAN/vBBUP. Additionallyor alternatively, one or more of the RAN nodes 311 may be nextgeneration eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA userplane and control plane protocol terminations toward the UEs 301, andare connected to a 5GC (e.g., CN 520 of FIG. 5) via an NG interface(discussed infra).

In V2X scenarios, one or more of the RAN nodes 311 may be or act asRSUs. The term “Road Side Unit” or “RSU” may refer to any transportationinfrastructure entity used for V2X communications. An RSU can beimplemented in or by a suitable RAN node or a stationary (or relativelystationary) UE, where an RSU implemented in or by a UE may be referredto as a “UE-type RSU,” an RSU implemented in or by an eNB may bereferred to as an “eNB-type RSU,” an RSU implemented in or by a gNB maybe referred to as a “gNB-type RSU,” and the like. In one example, an RSUis a computing device coupled with radio frequency circuitry located ona roadside that provides connectivity support to passing vehicle UEs 301(vUEs 301). The RSU may also include internal data storage circuitry tostore intersection map geometry, traffic statistics, media, as well asapplications/software to sense and control ongoing vehicular andpedestrian traffic. The RSU may operate on the 5.9 GHz Direct ShortRange Communications (DSRC) band to provide very low latencycommunications required for high speed events, such as crash avoidance,traffic warnings, and the like. Additionally or alternatively, the RSUmay operate on the cellular V2X band to provide the aforementioned lowlatency communications, as well as other cellular communicationsservices. Additionally or alternatively, the RSU may operate as a Wi-Fihotspot (2.4 GHz band) and/or provide connectivity to one or morecellular networks to provide uplink and downlink communications. Thecomputing device(s) and some or all of the radiofrequency circuitry ofthe RSU may be packaged in a weatherproof enclosure suitable for outdoorinstallation, and can include a network interface controller to providea wired connection (e.g., Ethernet) to a traffic signal controllerand/or a backhaul network.

Any of the RAN nodes 311 can terminate the air interface protocol andcan be the first point of contact for the UEs 301. In some embodiments,any of the RAN nodes 311 can fulfill various logical functions for theRAN 310 including, but not limited to, radio network controller (RNC)functions such as radio bearer management, uplink and downlink dynamicradio resource management and data packet scheduling, and mobilitymanagement.

In some embodiments, the UEs 301 can be configured to communicate usingOFDM communication signals with each other or with any of the RAN nodes311 over a multicarrier communication channel in accordance with variouscommunication techniques, such as, but not limited to, an OFDMAcommunication technique (e.g., for downlink communications) or a SC-FDMAcommunication technique (e.g., for uplink and ProSe or sidelinkcommunications), although the scope of the embodiments is not limited inthis respect. The OFDM signals can comprise a plurality of orthogonalsubcarriers.

In some embodiments, a downlink resource grid can be used for downlinktransmissions from any of the RAN nodes 311 to the UEs 301, while uplinktransmissions can utilize similar techniques. The grid can be atime-frequency grid, called a resource grid or time-frequency resourcegrid, which is the physical resource in the downlink in each slot. Sucha time-frequency plane representation is a common practice for OFDMsystems, which makes it intuitive for radio resource allocation. Eachcolumn and each row of the resource grid corresponds to one OFDM symboland one OFDM subcarrier, respectively. The duration of the resource gridin the time domain corresponds to one slot in a radio frame. Thesmallest time-frequency unit in a resource grid is denoted as a resourceelement. Each resource grid comprises a number of resource blocks, whichdescribe the mapping of certain physical channels to resource elements.Each resource block comprises a collection of resource elements; in thefrequency domain, this may represent the smallest quantity of resourcesthat currently can be allocated. There are several different physicaldownlink channels that are conveyed using such resource blocks.

In accordance with various embodiments, the UEs 301 and the RAN nodes311 communicate data (for example, transmit and receive) data over alicensed medium (also referred to as the “licensed spectrum” and/or the“licensed band”) and an unlicensed shared medium (also referred to asthe “unlicensed spectrum” and/or the “unlicensed band”). The licensedspectrum can include channels that operate in the frequency range ofapproximately 400 MHz to approximately 3.8 GHz, whereas the unlicensedspectrum can include the 5 GHz band.

To operate in the unlicensed spectrum, the UEs 301 and the RAN nodes 311may operate using LAA, eLAA, and/or feLAA mechanisms. In theseimplementations, the UEs 301 and the RAN nodes 311 may perform one ormore known medium-sensing operations and/or carrier-sensing operationsin order to determine whether one or more channels in the unlicensedspectrum is unavailable or otherwise occupied prior to transmitting inthe unlicensed spectrum. The medium/carrier sensing operations may beperformed according to a listen-before-talk (LBT) protocol.

LBT is a mechanism whereby equipment (for example, UEs 301, RAN nodes311, etc.) senses a medium (for example, a channel or carrier frequency)and transmits when the medium is sensed to be idle (or when a specificchannel in the medium is sensed to be unoccupied). The medium sensingoperation can include CCA, which utilizes at least ED to determine thepresence or absence of other signals on a channel in order to determineif a channel is occupied or clear. This LBT mechanism allowscellular/LAA networks to coexist with incumbent systems in theunlicensed spectrum and with other LAA networks. ED can include sensingRF energy across an intended transmission band for a period of time andcomparing the sensed RF energy to a predefined or configured threshold.

Typically, the incumbent systems in the 5 GHz band are WLANs based onIEEE 802.11 technologies. WLAN employs a contention-based channel accessmechanism, called CSMA/CA. Here, when a WLAN node (e.g., a mobilestation (MS) such as UE 301, AP 306, or the like) intends to transmit,the WLAN node may first perform CCA before transmission. Additionally, abackoff mechanism is used to avoid collisions in situations where morethan one WLAN node senses the channel as idle and transmits at the sametime. The backoff mechanism may be a counter that is drawn randomlywithin the CWS, which is increased exponentially upon the occurrence ofcollision and reset to a minimum value when the transmission succeeds.The LBT mechanism designed for LAA is somewhat similar to the CSMA/CA ofWLAN. In some embodiments, the LBT procedure for DL or UL transmissionbursts including PDSCH or PUSCH transmissions, respectively, may have anLAA contention window that is variable in length between X and Y ECCAslots, where X and Y are minimum and maximum values for the CWSs forLAA. In one example, the minimum CWS for an LAA transmission may be 9microseconds (s); however, the size of the CWS and a MCOT (for example,a transmission burst) may be based on governmental regulatoryrequirements.

The LAA mechanisms are built upon CA technologies of LTE-Advancedsystems. In CA, each aggregated carrier is referred to as a CC. A CC mayhave a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz and a maximum of fiveCCs can be aggregated, and therefore, a maximum aggregated bandwidth is100 MHz. In FDD systems, the number of aggregated carriers can bedifferent for DL and UL, where the number of UL CCs is equal to or lowerthan the number of DL component carriers. In some cases, individual CCscan have a different bandwidth than other CCs. In TDD systems, thenumber of CCs as well as the bandwidths of each CC is usually the samefor DL and UL.

CA also comprises individual serving cells to provide individual CCs.The coverage of the serving cells may differ, for example, because CCson different frequency bands can experience different pathloss. Aprimary service cell or PCell provides a PCC for both UL and DL, andhandles RRC and NAS related activities. The other serving cells arereferred to as SCells, and each SCell provides an individual SCC forboth UL and DL. The SCCs may be added and removed as required, whilechanging the PCC may require the UE 301 to undergo a handover. In LAA,eLAA, and feLAA, some or all of the SCells may operate in the unlicensedspectrum (referred to as “LAA SCells”), and the LAA SCells are assistedby a PCell operating in the licensed spectrum. When a UE is configuredwith more than one LAA SCell, the UE may receive UL grants on theconfigured LAA SCells indicating different PUSCH starting positionswithin a same subframe.

The PDSCH carries user data and higher-layer signaling to the UEs 301.The PDCCH carries information about the transport format and resourceallocations related to the PDSCH channel, among other things. It mayalso inform the UEs 301 about the transport format, resource allocation,and HARQ information related to the uplink shared channel. Typically,downlink scheduling (assigning control and shared channel resourceblocks to the UE 301 b within a cell) may be performed at any of the RANnodes 311 based on channel quality information fed back from any of theUEs 301. The downlink resource assignment information may be sent on thePDCCH used for (e.g., assigned to) each of the UEs 301.

The PDCCH uses CCEs to convey the control information. Before beingmapped to resource elements, the PDCCH complex-valued symbols may firstbe organized into quadruplets, which may then be permuted using asub-block interleaver for rate matching. Each PDCCH may be transmittedusing one or more of these CCEs, where each CCE may correspond to ninesets of four physical resource elements known as REGs. Four QuadraturePhase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCHcan be transmitted using one or more CCEs, depending on the size of theDCI and the channel condition. There can be four or more different PDCCHformats defined in LTE with different numbers of CCEs (e.g., aggregationlevel, L=1, 2, 4, or 8).

Some embodiments may use concepts for resource allocation for controlchannel information that are an extension of the above-describedconcepts. For example, some embodiments may utilize an EPDCCH that usesPDSCH resources for control information transmission. The EPDCCH may betransmitted using one or more ECCEs. Similar to above, each ECCE maycorrespond to nine sets of four physical resource elements known as anEREGs. An ECCE may have other numbers of EREGs in some situations.

The RAN nodes 311 can be configured to communicate with one another viainterface 212. In some embodiments where the system 300 is an LTE system(e.g., when CN 320 is an EPC 420 as in FIG. 4), the interface 212 may bean X2 interface 212. The X2 interface may be defined between two or moreRAN nodes 311 (e.g., two or more eNBs and the like) that connect to EPC320, and/or between two eNBs connecting to EPC 320. In some embodiments,the X2 interface can include an X2 user plane interface (X2-U) and an X2control plane interface (X2-C). The X2-U provides flow controlmechanisms for user data packets transferred over the X2 interface, andmay be used to communicate information about the delivery of user databetween eNBs. For example, the X2-U provides specific sequence numberinformation for user data transferred from a MeNB to an SeNB;information about successful in sequence delivery of PDCP PDUs to a UE301 from an SeNB for user data; information of PDCP PDUs that were notdelivered to a UE 301; information about a current minimum desiredbuffer size at the SeNB for transmitting to the UE user data; and thelike. The X2-C provides intra-LTE access mobility functionality,including context transfers from source to target eNBs, user planetransport control, etc.; load management functionality; as well asinter-cell interference coordination functionality.

In some embodiments where the system 300 is a 5G or NR system (e.g.,when CN 320 is an 5GC 520 as in FIG. 5), the interface 212 may be an Xninterface 212. The Xn interface is defined between two or more RAN nodes311 (e.g., two or more Next Generation NodeBs (gNBs) and the like) thatconnect to 5GC 320, between a RAN node 311 (e.g., a gNB) connecting to5GC 320 and an evolved NodeB (eNB), and/or between two eNBs connectingto 5GC 320. In some embodiments, the Xn interface can include an Xn userplane (Xn-U) interface and an Xn control plane (Xn-C) interface. TheXn-U provides non-guaranteed delivery of user plane Protocol Data Units(PDUs) and support/provide data forwarding and flow controlfunctionality. The Xn-C provides management and error handlingfunctionality, functionality to manage the Xn-C interface; mobilitysupport for UE 301 in a connected mode (e.g., CM-CONNECTED) includingfunctionality to manage the UE mobility for connected mode between oneor more RAN nodes 311. The mobility support can include context transferfrom an old (source) serving RAN node 311 to new (target) serving RANnode 311; and control of user plane tunnels between old (source) servingRAN node 311 to new (target) serving RAN node 311. A protocol stack ofthe Xn-U can include a transport network layer built on InternetProtocol (IP) transport layer, and a GPRS Tunnelling Protocol for UserPlane (GTP-U) layer on top of a User Datagram Protocol (UDP) and/or IPlayer(s) to carry user plane PDUs. The Xn-C protocol stack can includean application layer signaling protocol (referred to as Xn ApplicationProtocol (Xn-AP)) and a transport network layer that is built on StreamControl Transmission Protocol (SCTP). The SCTP may be on top of an IPlayer, and provides the guaranteed delivery of application layermessages. In the transport IP layer, point-to-point transmission is usedto deliver the signaling PDUs. In other implementations, the Xn-Uprotocol stack and/or the Xn-C protocol stack may be same or similar tothe user plane and/or control plane protocol stack(s) shown anddescribed herein.

The RAN 310 is shown to be communicatively coupled to a core network—inthis embodiment, core network (CN) 320. The CN 320 may comprise aplurality of network elements 322, which are configured to offer variousdata and telecommunications services to customers/subscribers (e.g.,users of UEs 301) who are connected to the CN 320 via the RAN 310. Thecomponents of the CN 320 can be implemented in one physical node orseparate physical nodes including components to read and executeinstructions from a machine-readable or computer-readable medium (e.g.,a non-transitory machine-readable storage medium). In some embodiments,Network Functions Virtualization (NFV) may be utilized to virtualize anyor all of the above-described network node functions via executableinstructions stored in one or more computer-readable storage mediums(described in further detail below). A logical instantiation of the CN320 may be referred to as a network slice, and a logical instantiationof a portion of the CN 320 may be referred to as a network sub-slice.NFV architectures and infrastructures may be used to virtualize one ormore network functions, alternatively performed by proprietary hardware,onto physical resources comprising a combination of industry-standardserver hardware, storage hardware, or switches. In other words, NFVsystems can be used to execute virtual or reconfigurable implementationsof one or more EPC components/functions.

Generally, the application server 330 may be an element offeringapplications that use IP bearer resources with the core network (e.g.,Universal Mobile Telecommunications System (UMTS) Packet Services (PS)domain, LTE PS data services, etc.). The application server 330 can alsobe configured to support one or more communication services (e.g., VoIPsessions, PTT sessions, group communication sessions, social networkingservices, etc.) for the UEs 301 via the CN 320.

In some embodiments, the CN 320 may be a 5GC (referred to as “5GC 320”or the like), and the RAN 310 may be connected with the CN 320 via an NGinterface 313. In some embodiments, the NG interface 313 may be splitinto two parts, an NG user plane (NG-U) interface 314, which carriestraffic data between the RAN nodes 311 and a UPF, and the S1 controlplane (NG-C) interface 315, which is a signaling interface between theRAN nodes 311 and AMFs. Embodiments where the CN 320 is a 5GC 320 arediscussed in more detail with regard to FIG. 5.

In some embodiments, the CN 320 may be a 5G CN (referred to as “5GC 320”or the like), while in other embodiments, the CN 320 may be an EPC).Where CN 320 is an EPC (referred to as “EPC 320” or the like), the RAN310 may be connected with the CN 320 via an S1 interface 313. In someembodiments, the S1 interface 313 may be split into two parts, an S1user plane (S1-U) interface 314, which carries traffic data between theRAN nodes 311 and the S-GW, and the S1-MME interface 315, which is asignaling interface between the RAN nodes 311 and MMEs. An examplearchitecture wherein the CN 320 is an EPC 320 is illustrated in FIG. 4.

Exemplary Architectures

FIG. 4 illustrates an example architecture of a system 400 including afirst CN 420 in accordance with various embodiments. In this example,system 400 may implement the LTE standard wherein the CN 420 is an EPC420 that corresponds with CN 320 of FIG. 3. Additionally, the UE 301 maybe the same or similar as the UEs 301 of FIG. 3, and the E-UTRAN 310 maybe a RAN that is the same or similar to the RAN 310 of FIG. 3, and whichcan include RAN nodes 311 discussed previously. The CN 420 may compriseMobility Management Entities (MMEs) 421, a Serving Gateway (S-GW) 422, aPDN Gateway (P-GW) 423, a Home Subscriber Server (HSS) 424, and aServing GPRS Support Node (SGSN) 425.

The MMEs 421 may be similar in function to the control plane of legacySGSN, and may implement Mobility Management (MM) functions to keep trackof the current location of a UE 301. The MMEs 421 may perform various MMprocedures to manage mobility aspects in access such as gatewayselection and tracking area list management. MM (also referred to as“EPS MM” or “EMM” in E-UTRAN systems) may refer to all applicableprocedures, methods, data storage, etc. that are used to maintainknowledge about a present location of the UE 301, provide user identityconfidentiality, and/or perform other like services tousers/subscribers. Each UE 301 and the MME 421 can include an MM or EMMsublayer, and an MM context may be established in the UE 301 and the MME421 when an attach procedure is successfully completed. The MM contextmay be a data structure or database object that stores MM-relatedinformation of the UE 301. The MMEs 421 may be coupled with the HSS 424via an S6a reference point, coupled with the SGSN 425 via an S3reference point, and coupled with the S-GW 422 via an S11 referencepoint.

The SGSN 425 may be a node that serves the UE 301 by tracking thelocation of an individual UE 301 and performing security functions. Inaddition, the SGSN 425 may perform Inter-EPC node signaling for mobilitybetween 2G/3G and E-UTRAN 3GPP access networks; PDN and S-GW selectionas specified by the MMEs 421; handling of UE 301 time zone functions asspecified by the MMEs 421; and MME selection for handovers to E-UTRAN3GPP access network. The S3 reference point between the MMEs 421 and theSGSN 425 may enable user and bearer information exchange for inter-3GPPaccess network mobility in idle and/or active states.

The HSS 424 may comprise a database for network users, includingsubscription-related information to support the network entities'handling of communication sessions. The EPC 420 may comprise one orseveral HSSs 424, depending on the number of mobile subscribers, on thecapacity of the equipment, on the organization of the network, etc. Forexample, the HSS 424 can provide support for routing/roaming,authentication, authorization, naming/addressing resolution, locationdependencies, etc. An S6a reference point between the HSS 424 and theMMEs 421 may enable transfer of subscription and authentication data forauthenticating/authorizing user access to the EPC 420 between HSS 424and the MMEs 421.

The S-GW 422 may terminate the S1 for the user plane (S1-U) interfacetoward the RAN 310, and routes data packets between the RAN 310 and theEPC 420. In addition, the S-GW 422 may be a local mobility anchor pointfor inter-RAN node handovers and also provides an anchor for inter-3GPPmobility. Other responsibilities can include lawful intercept, charging,and some policy enforcement. The S11 reference point between the S-GW422 and the MMEs 421 provides a control plane between the MMEs 421 andthe S-GW 422. The S-GW 422 may be coupled with the P-GW 423 via an S5reference point.

The P-GW 423 may terminate an SGi interface toward a PDN 430. The P-GW423 may route data packets between the EPC 420 and external networkssuch as a network including the application server 330 (alternativelyreferred to as an “AF”) via an IP interface 325 (see e.g., FIG. 3). Insome embodiments, the P-GW 423 may be communicatively coupled to anapplication server (application server 330 of FIG. 3 or PDN 430 in FIG.4) via an IP communications interface 325 (see, e.g., FIG. 3). The S5reference point between the P-GW 423 and the S-GW 422 provides userplane tunneling and tunnel management between the P-GW 423 and the S-GW422. The S5 reference point may also be used for S-GW 422 relocation dueto UE 301 mobility and if the S-GW 422 needs to connect to anon-collocated P-GW 423 for the required PDN connectivity. The P-GW 423may further include a node for policy enforcement and charging datacollection (e.g., PCEF (not shown)). Additionally, the SGi referencepoint between the P-GW 423 and the packet data network (PDN) 430 may bean operator external public, a private PDN, or an intra operator packetdata network, for example, for provision of IMS services. The P-GW 423may be coupled with a PCRF 426 via a Gx reference point.

PCRF 426 is the policy and charging control element of the EPC 420. In anon-roaming scenario, there may be a single PCRF 426 in the Home PublicLand Mobile Network (HPLMN) associated with a UE 301's Internet ProtocolConnectivity Access Network (IP-CAN) session. In a roaming scenario withlocal breakout of traffic, there may be two PCRFs associated with a UE301's IP-CAN session, a Home PCRF (H-PCRF) within an HPLMN and a VisitedPCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). ThePCRF 426 may be communicatively coupled to the application server 430via the P-GW 423. The application server 430 may signal the PCRF 426 toindicate a new service flow and select the appropriate QoS and chargingparameters. The PCRF 426 may provision this rule into a PCEF (not shown)with the appropriate TFT and QCI, which commences the QoS and chargingas specified by the application server 430. The Gx reference pointbetween the PCRF 426 and the P-GW 423 may allow for the transfer of QoSpolicy and charging rules from the PCRF 426 to PCEF in the P-GW 423. AnRx reference point may reside between the PDN 430 (or “AF 430”) and thePCRF 426.

FIG. 5 illustrates an architecture of a system 500 including a second CN520 in accordance with various embodiments. The system 500 is shown toinclude a UE 501, which may be the same or similar to the UEs 301 and UE301 discussed previously; a (R)AN 510, which may be the same or similarto the RAN 310 and RAN 410 discussed previously, and which can includeRAN nodes 311 discussed previously; and a data network (DN) 503, whichmay be, for example, operator services, Internet access or 3rd partyservices; and a 5GC 520. The 5GC 520 can include an AuthenticationServer Function (AUSF)522; an Access and Mobility Management Function(AMF) 521; a Session Management Function (SMF) 524; a Network ExposureFunction (NEF) 523; a PCF 526; a NF Repository Function (NRF) 525; a UDM527; an Application Function (AF) 528; a User Plane Function (UPF) 502;and a Network Slice Selection Function (NSSF) 529.

The UPF 502 may act as an anchor point for intra-RAT and inter-RATmobility, an external PDU session point of interconnect to DN 503, and abranching point to support multi-homed PDU session. The UPF 502 may alsoperform packet routing and forwarding, perform packet inspection,enforce the user plane part of policy rules, lawfully intercept packets(UP collection), perform traffic usage reporting, perform QoS handlingfor a user plane (e.g., packet filtering, gating, UL/DL rateenforcement), perform Uplink Traffic verification (e.g., SDF to QoS flowmapping), transport level packet marking in the uplink and downlink, andperform downlink packet buffering and downlink data notificationtriggering. UPF 502 can include an uplink classifier to support routingtraffic flows to a data network. The DN 503 may represent variousnetwork operator services, Internet access, or third party services. DN503 can include, or be similar to, application server 330 discussedpreviously. The UPF 502 interacts with the SMF 524 via an N4 referencepoint between the SMF 524 and the UPF 502.

The AUSF 522 stores data for authentication of UE 501 and handleauthentication-related functionality. The AUSF 522 may facilitate acommon authentication framework for various access types. The AUSF 522communicate with the AMF 521 via an N12 reference point between the AMF521 and the AUSF 522; and communicate with the UDM 527 via an N13reference point between the UDM 527 and the AUSF 522. Additionally, theAUSF 522 can exhibit an Nausf service-based interface.

The AMF 521 may be responsible for registration management (e.g., forregistering UE 501, etc.), connection management, reachabilitymanagement, mobility management, and lawful interception of AMF-relatedevents, and access authentication and authorization. The AMF 521 may bea termination point for the N11 reference point between the AMF 521 andthe SMF 524. The AMF 521 provides transport for Session Management (SM)messages between the UE 501 and the SMF 524, and act as a transparentpro15 for routing SM messages. AMF 521 may also provide transport forShort Message Service (SMS) messages between UE 501 and an SMS Function(SMSF) (not illustrated in FIG. 5). AMF 521 may act as a Security AnchorFunction (SEAF), which can include interaction with the AUSF 522 and theUE 501, receipt of an intermediate key that was established as a resultof the UE 501 authentication process. Where Universal SubscriberIdentity Module (USIM) based authentication is used, the AMF 521 mayretrieve the security material from the AUSF 522. AMF 521 may alsoinclude a Security Context Management (SCM) function, which receives akey from the SEA that it uses to derive access-network specific keys.Furthermore, AMF 521 may be a termination point of a RAN CP interface,which can include or be an N2 reference point between the (R)AN 510 andthe AMF 521; and the AMF 521 may be a termination point of NAS (N1)signalling, and perform NAS ciphering and integrity protection.

AMF 521 may also support NAS signalling with a UE 501 over an N3 IWFinterface. The N3IWF may be used to provide access to untrustedentities. N3IWF may be a termination point for the N2 interface betweenthe (R)AN 510 and the AMF 521 for the control plane, and may be atermination point for the N3 reference point between the (R)AN 510 andthe UPF 502 for the user plane. As such, the AMF 521 handles N2signalling from the SMF 524 and the AMF 521 for Protocol Data Unit (PDU)sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3tunneling, mark N3 user-plane packets in the uplink, and enforce QoScorresponding to N3 packet marking taking into account QoS requirementsassociated with such marking received over N2. N3IWF may also relayuplink and downlink control-plane NAS signalling between the UE 501 andAMF 521 via an N1 reference point between the UE 501 and the AMF 521,and relay uplink and downlink user-plane packets between the UE 501 andUPF 502. The N3IWF also provides mechanisms for IPsec tunnelestablishment with the UE 501. The AMF 521 can exhibit an Namfservice-based interface, and may be a termination point for an N14reference point between two AMFs 521 and an N17 reference point betweenthe AMF 521 and a 5G-EIR (not illustrated in FIG. 5).

The UE 501 may need to register with the AMF 521 in order to receivenetwork services. Registration Management (RM) is used to register orderegister the UE 501 with the network (e.g., AMF 521), and establish aUE context in the network (e.g., AMF 521). The UE 501 may operate in anRM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTEREDstate, the UE 501 is not registered with the network, and the UE contextin AMF 521 holds no valid location or routing information for the UE 501so the UE 501 is not reachable by the AMF 521. In the RM-REGISTEREDstate, the UE 501 is registered with the network, and the UE context inAMF 521 may hold a valid location or routing information for the UE 501so the UE 501 is reachable by the AMF 521. In the RM-REGISTERED state,the UE 501 may perform mobility Registration Update procedures, performperiodic Registration Update procedures triggered by expiration of theperiodic update timer (e.g., to notify the network that the UE 501 isstill active), and perform a Registration Update procedure to update UEcapability information or to re-negotiate protocol parameters with thenetwork, among others.

The AMF 521 stores one or more RM contexts for the UE 501, where each RMcontext is associated with a specific access to the network. The RMcontext may be a data structure, database object, etc. that indicates orstores, inter alia, a registration state per access type and theperiodic update timer. The AMF 521 may also store a 5GC MobilityManagement (MM) context that may be the same or similar to the (E)MMcontext discussed previously. In various embodiments, the AMF 521 storesa CE mode B Restriction parameter of the UE 501 in an associated MMcontext or RM context. The AMF 521 may also derive the value, whenneeded, from the UE's usage setting parameter already stored in the UEcontext (and/or MM/RM context).

Connection Management (CM) establishes and releases a signalingconnection between the UE 501 and the AMF 521 over the N1 interface. Thesignaling connection is used to enable NAS signaling exchange betweenthe UE 501 and the CN 520, and comprises both the signaling connectionbetween the UE and the AN (e.g., Radio Resource Control (RRC) connectionor UE-N3IWF connection for non-3GPP access) and the N2 connection forthe UE 501 between the AN (e.g., RAN 510) and the AMF 521. The UE 501may operate in one of two CM states, CM-IDLE mode or CM-CONNECTED mode.When the UE 501 is operating in the CM-IDLE state/mode, the UE 501 mayhave no Non-Access Stratum (NAS) signaling connection established withthe AMF 521 over the N1 interface, and there may be (R)AN 510 signalingconnection (e.g., N2 and/or N3 connections) for the UE 501. When the UE501 is operating in the CM-CONNECTED state/mode, the UE 501 may have anestablished NAS signaling connection with the AMF 521 over the N1interface, and there may be a (R)AN 510 signaling connection (e.g., N2and/or N3 connections) for the UE 501. Establishment of an N2 connectionbetween the (R)AN 510 and the AMF 521 may cause the UE 501 to transitionfrom CM-IDLE mode to CM-CONNECTED mode, and the UE 501 may transitionfrom the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling betweenthe (R)AN 510 and the AMF 521 is released.

The SMF 524 is responsible for Session Management (SM) (e.g., sessionestablishment, modify and release, including tunnel maintain between UPFand AN node); UE IP address allocation and management (includingoptional authorization); selection and control of User Plane (UP)function; configuring traffic steering at UPF to route traffic to properdestination; termination of interfaces toward policy control functions;controlling part of policy enforcement and QoS; lawful intercept (for SMevents and interface to LI system); termination of SM parts of NASmessages; downlink data notification; initiating AN specific SMinformation, sent via Access and Mobility Management Function (AMF) overN2 to AN; and determining Session and Service Continuity (SSC) mode of asession. SM may refer to management of a Protocol Data Unit (PDU)session, and a PDU session or “session” may refer to a PDU connectivityservice that provides or enables the exchange of PDUs between a UE 501and a data network (DN) 503 identified by a Data Network Name (DNN). PDUsessions may be established upon UE 501 request, modified upon UE 501and 5GC 520 request, and released upon UE 501 and 5GC 520 request usingNAS SM signaling exchanged over the N1 reference point between the UE501 and the SMF 524. Upon request from an application server, the 5GC520 may trigger a specific application in the UE 501. In response toreceipt of the trigger message, the UE 501 may pass the trigger message(or relevant parts/information of the trigger message) to one or moreidentified applications in the UE 501. The identified application(s) inthe UE 501 may establish a PDU session to a specific DNN. The SMF 524may check whether the UE 501 requests are compliant with usersubscription information associated with the UE 501. In this regard, theSMF 524 may retrieve and/or request to receive update notifications onSMF 524 level subscription data from the UDM 527.

The SMF 524 can include the following roaming functionality: handlinglocal enforcement to apply QoS SLAs (VPLMN); charging data collectionand charging interface (VPLMN); lawful intercept (in VPLMN for SM eventsand interface to LI system); and support for interaction with externalDN for transport of signalling for PDU sessionauthorization/authentication by external DN. An N16 reference pointbetween two SMFs 524 may be included in the system 500, which may bebetween another SMF 524 in a visited network and the SMF 524 in the homenetwork in roaming scenarios. Additionally, the SMF 524 can exhibit theNsmf service-based interface.

The NEF 523 provides means for securely exposing the services andcapabilities provided by 3GPP network functions for third party,internal exposure/re-exposure, Application Functions (e.g., AF 528),edge computing or fog computing systems, etc. In such embodiments, theNEF 523 may authenticate, authorize, and/or throttle the AFs. NEF 523may also translate information exchanged with the AF 528 and informationexchanged with internal network functions. For example, the NEF 523 maytranslate between an AF-Service-Identifier and an internal 5GCinformation. NEF 523 may also receive information from other networkfunctions (NFs) based on exposed capabilities of other networkfunctions. This information may be stored at the NEF 523 as structureddata, or at a data storage NF using standardized interfaces. The storedinformation can then be re-exposed by the NEF 523 to other NFs and AFs,and/or used for other purposes such as analytics. Additionally, the NEF523 can exhibit an Nnef service-based interface.

The NRF 525 supports service discovery functions, receive NetworkFunction (NF) discovery requests from NF instances, and provide theinformation of the discovered NF instances to the NF instances. NRF 525also maintains information of available NF instances and their supportedservices. As used herein, the terms “instantiate,” “instantiation,” andthe like may refer to the creation of an instance, and an “instance” mayrefer to a concrete occurrence of an object, which may occur, forexample, during execution of program code. Additionally, the NRF 525 canexhibit the Nnrf service-based interface.

The PCF 526 provides policy rules to control plane function(s) toenforce them, and may also support unified policy framework to governnetwork behaviour. The PCF 526 may also implement an Front End (FE) toaccess subscription information relevant for policy decisions in a UDRof the UDM 527. The PCF 526 communicate with the AMF 521 via an N15reference point between the PCF 526 and the AMF 521, which can include aPCF 526 in a visited network and the AMF 521 in case of roamingscenarios. The PCF 526 communicate with the AF 528 via an N5 referencepoint between the PCF 526 and the AF 528; and with the SMF 524 via an N7reference point between the PCF 526 and the SMF 524. The system 500and/or CN 520 may also include an N24 reference point between the PCF526 (in the home network) and a PCF 526 in a visited network.Additionally, the PCF 526 can exhibit an Npcf service-based interface.

The UDM 527 handles subscription-related information to support thenetwork entities' handling of communication sessions, and storessubscription data of UE 501. For example, subscription data may becommunicated between the UDM 527 and the AMF 521 via an N8 referencepoint between the UDM 527 and the AMF. The UDM 527 can include twoparts, an application Front End (FE) and a UDR (the FE and UDR are notillustrated in FIG. 5). The UDR stores subscription data and policy datafor the UDM 527 and the PCF 526, and/or structured data for exposure andapplication data (including PFDs for application detection, applicationrequest information for multiple UEs 501) for the NEF 523. The Nudrservice-based interface may be exhibited by the UDR 221 to allow the UDM527, PCF 526, and NEF 523 to access a particular set of the stored data,as well as to read, update (e.g., add, modify), delete, and subscribe tonotification of relevant data changes in the UDR. The UDM can include aUDM-FE, which is in charge of processing credentials, locationmanagement, subscription management and so on. Several different frontends can serve the same user in different transactions. The UDM-FEaccesses subscription information stored in the UDR and performsauthentication credential processing, user identification handling,access authorization, registration/mobility management, and subscriptionmanagement. The UDR interacts with the SMF 524 via an N10 referencepoint between the UDM 527 and the SMF 524. UDM 527 may also support SMSmanagement, wherein an SMS-FE implements the similar application logicas discussed previously. Additionally, the UDM 527 can exhibit the Nudmservice-based interface.

The AF 528 provides application influence on traffic routing, provideaccess to the NCE, and interact with the policy framework for policycontrol. The NCE is a mechanism that allows the 5GC 520 and AF 528 toprovide information to each other via NEF 523, which may be used foredge computing implementations. In such implementations, the networkoperator and third party services can be hosted close to the UE 501access point of attachment to achieve an efficient service deliverythrough the reduced end-to-end latency and load on the transportnetwork. For edge computing implementations, the 5GC can select a UPF502 close to the UE 501 and execute traffic steering from the UPF 502 toDN 503 via the N6 interface. This may be based on the UE subscriptiondata, UE location, and information provided by the AF 528. In this way,the AF 528 influences UPF (re)selection and traffic routing. Based onoperator deployment, when AF 528 is considered to be a trusted entity,the network operator permits AF 528 to interact directly with relevantNFs. Additionally, the AF 528 can exhibit an Naf service-basedinterface.

The NSSF 529 selects a set of network slice instances serving the UE501. The NSSF 529 also determines allowed Network Slice SelectionAssistance Information (NSSAI) and the mapping to the subscribedSingle-NSSAIs (S-NSSAIs), if needed. The NSSF 529 also determines theAccess and Mobility Management Function (AMF) set to be used to servethe UE 501, or a list of candidate AMF(s) 521 based on a suitableconfiguration and possibly by querying the NRF 525. The selection of aset of network slice instances for the UE 501 may be triggered by theAMF 521 with which the UE 501 is registered by interacting with the NSSF529, which may lead to a change of AMF 521. The NSSF 529 interacts withthe AMF 521 via an N22 reference point between AMF 521 and NSSF 529; andcommunicate with another NSSF 529 in a visited network via an N31reference point (not illustrated in FIG. 5). Additionally, the NSSF 529can exhibit an Nnssf service-based interface.

As discussed previously, the CN 520 can include an SMS Function (SMSF),which may be responsible for Short Message Service (SMS) subscriptionchecking and verification, and relaying SM messages to/from the UE 501to/from other entities, such as an SMS-GMSC/IWMSC/SMS-router. The SMSalso interacts with AMF 521 and UDM 527 for a notification procedurethat the UE 501 is available for SMS transfer (e.g., set a UE notreachable flag, and notifying UDM 527 when UE 501 is available for SMS).

The CN 520 may also include other elements that are not illustrated inFIG. 5, such as a Data Storage system/architecture, a 5G-EquipmentIdentity Register (EIR), a Security Edge Protection Pro15 (SEPP), andthe like. The Data Storage system can include a Structured Data StorageFunction (SDSF), an Unstructured Data Storage Network Function (UDSF),and/or the like. Any Network Function (NF) stores and retrieveunstructured data into/from the UDSF (e.g., UE contexts), via N18reference point between any NF and the UDSF (not illustrated in FIG. 5).Individual NFs may share a UDSF for storing their respectiveunstructured data or individual NFs may each have their own UDSF locatedat or near the individual NFs. Additionally, the UDSF can exhibit anNudsf service-based interface (not illustrated in FIG. 5). The 5G-EIRmay be an NF that checks the status of PEI for determining whetherparticular equipment/entities are blacklisted from the network; and theSEPP may be a non-transparent pro15 that performs topology hiding,message filtering, and policing on inter-Public Land Mobile Network(PLMN) control plane interfaces.

Additionally, there may be many more reference points and/orservice-based interfaces between the NF services in the NFs; however,these interfaces and reference points have been omitted from FIG. 5 forclarity. In one example, the CN 520 can include an Nx interface, whichis an inter-CN interface between the MME (e.g., MME 1 121) and the AMF521 in order to enable interworking between CN 520 and CN 1 120. Otherexample interfaces/reference points can include an N5g-EIR service-basedinterface exhibited by a 5G-EIR, an N27 reference point between the NFRepository Function (NRF) in the visited network and the NRF in the homenetwork; and an N31 reference point between the Network Slice SelectionFunction (NSSF) in the visited network and the NSSF in the home network.

Exemplary Infrastructure Equipment

FIG. 6 illustrates an example of infrastructure equipment 600 inaccordance with various embodiments. The infrastructure equipment 600(or “system 600”) can be implemented as a base station, radio head, RANnode such as the RAN nodes 311 and/or AP 306 shown and describedpreviously, application server(s) 330, and/or any other element/devicediscussed herein. In other examples, the system 600 could be implementedin or by a UE.

The system 600 includes application circuitry 605, baseband circuitry610, one or more radio front end modules (RFEMs) 615, memory circuitry620, power management integrated circuitry (PMIC) 625, power teecircuitry 630, network controller circuitry 635, network interfaceconnector 640, satellite positioning circuitry 645, and user interface650. In some embodiments, the device 600 can include additional elementssuch as, for example, memory/storage, display, camera, sensor, orinput/output (I/O) interface. In other embodiments, the componentsdescribed below may be included in more than one device. For example,said circuitries may be separately included in more than one device forCloud Radio Access Network (CRAN), vBBU, or other like implementations.

Application circuitry 605 includes circuitry such as, but not limited toone or more processors (or processor cores), cache memory, and one ormore of low drop-out voltage regulators (LDOs), interrupt controllers,serial interfaces such as SPI, I²C or universal programmable serialinterface module, real time clock (RTC), timer-counters includinginterval and watchdog timers, general purpose input/output (I/O or IO),memory card controllers such as Secure Digital (SD) MultiMediaCard (MMC)or similar, Universal Serial Bus (USB) interfaces, Mobile IndustryProcessor Interface (MIPI) interfaces and Joint Test Access Group (JTAG)test access ports. The processors (or cores) of the applicationcircuitry 605 may be coupled with or can include memory/storage elementsand can be configured to execute instructions stored in thememory/storage to enable various applications or operating systems torun on the system 600. In some embodiments, the memory/storage elementsmay be on-chip memory circuitry, which can include any suitable volatileand/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flashmemory, solid-state memory, and/or any other type of memory devicetechnology, such as those discussed herein.

The processor(s) of application circuitry 605 can include, for example,one or more processor cores (CPUs), one or more application processors,one or more graphics processing units (GPUs), one or more reducedinstruction set computing (RISC) processors, one or more Acorn RISCMachine (ARM) processors, one or more complex instruction set computing(CISC) processors, one or more digital signal processors (DSP), one ormore FPGAs, one or more PLDs, one or more ASICs, one or moremicroprocessors or controllers, or any suitable combination thereof. Insome embodiments, the application circuitry 605 may comprise, or may be,a special-purpose processor/controller to operate according to thevarious embodiments herein. As examples, the processor(s) of applicationcircuitry 605 can include one or more Intel Pentium®, Core®, or Xeon®processor(s); Advanced Micro Devices (AMD) Ryzen® processor(s),Accelerated Processing Units (APUs), or Epyc® processors; ARM-basedprocessor(s) licensed from ARM Holdings, Ltd. such as the ARM Cortex-Afamily of processors and the ThunderX2® provided by Cavium™, Inc.; aMIPS-based design from MIPS Technologies, Inc. such as MIPS WarriorP-class processors; and/or the like. In some embodiments, the system 600may not utilize application circuitry 605, and instead can include aspecial-purpose processor/controller to process IP data received from anEPC or 5GC, for example.

In some embodiments, the application circuitry 605 can include one ormore hardware accelerators, which may be microprocessors, programmableprocessing devices, or the like. The one or more hardware acceleratorscan include, for example, computer vision (CV) and/or deep learning (DL)accelerators. As examples, the programmable processing devices may beone or more a field-programmable devices (FPDs) such asfield-programmable gate arrays (FPGAs) and the like; programmable logicdevices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs(HCPLDs), and the like; ASICs such as structured ASICs and the like;programmable SoCs (PSoCs); and the like. In such implementations, thecircuitry of application circuitry 605 may comprise logic blocks orlogic fabric, and other interconnected resources that may be programmedto perform various functions, such as the procedures, methods,functions, etc. of the various embodiments discussed herein. In suchembodiments, the circuitry of application circuitry 605 can includememory cells (e.g., erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), flashmemory, static memory (e.g., static random access memory (SRAM),anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc.in look-up-tables (LUTs) and the like.

The baseband circuitry 610 can be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Thevarious hardware electronic elements of baseband circuitry 610 are to bediscussed below with regard to FIG. 8.

User interface circuitry 650 can include one or more user interfacesdesigned to enable user interaction with the system 600 or peripheralcomponent interfaces designed to enable peripheral component interactionwith the system 600. User interfaces can include, but are not limitedto, one or more physical or virtual buttons (e.g., a reset button), oneor more indicators (e.g., light emitting diodes (LEDs)), a physicalkeyboard or keypad, a mouse, a touchpad, a touchscreen, speakers orother audio emitting devices, microphones, a printer, a scanner, aheadset, a display screen or display device, etc. Peripheral componentinterfaces can include, but are not limited to, a nonvolatile memoryport, a universal serial bus (USB) port, an audio jack, a power supplyinterface, etc.

The radio front end modules (RFEMs) 615 may comprise a millimeter wave(mmWave) RFEM and one or more sub-mmWave radio frequency integratedcircuits (RFICs). In some embodiments, the one or more sub-mmWave RFICsmay be physically separated from the mmWave RFEM. The RFICs can includeconnections to one or more antennas or antenna arrays (see e.g., antennaarray 811 of FIG. 8 infra), and the RFEM may be connected to multipleantennas. In alternative implementations, both mmWave and sub-mmWaveradio functions can be implemented in the same physical RFEM 615, whichincorporates both mmWave antennas and sub-mmWave.

The memory circuitry 620 can include one or more of volatile memoryincluding dynamic random access memory (DRAM) and/or synchronous dynamicrandom access memory (SDRAM), and nonvolatile memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), magnetoresistiverandom access memory (MRAM), etc., and may incorporate thethree-dimensional (3D) cross-point (XPOINT) memories from Intel® andMicron®. Memory circuitry 620 can be implemented as one or more ofsolder down packaged integrated circuits, socketed memory modules andplug-in memory cards.

The PMIC 625 can include voltage regulators, surge protectors, poweralarm detection circuitry, and one or more backup power sources such asa battery or capacitor. The power alarm detection circuitry may detectone or more of brown out (under-voltage) and surge (over-voltage)conditions. The power tee circuitry 630 provides for electrical powerdrawn from a network cable to provide both power supply and dataconnectivity to the infrastructure equipment 600 using a single cable.

The network controller circuitry 635 provides connectivity to a networkusing a standard network interface protocol such as Ethernet, Ethernetover GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), orsome other suitable protocol. Network connectivity may be providedto/from the infrastructure equipment 600 via network interface connector640 using a physical connection, which may be electrical (commonlyreferred to as a “copper interconnect”), optical, or wireless. Thenetwork controller circuitry 635 can include one or more dedicatedprocessors and/or FPGAs to communicate using one or more of theaforementioned protocols. In some embodiments, the network controllercircuitry 635 can include multiple controllers to provide connectivityto other networks using the same or different protocols.

The positioning circuitry 645 includes circuitry to receive and decodesignals transmitted/broadcasted by a positioning network of a globalnavigation satellite system (GNSS). Examples of navigation satelliteconstellations (or GNSS) include United States' Global PositioningSystem (GPS), Russia's Global Navigation System (GLONASS), the EuropeanUnion's Galileo system, China's BeiDou Navigation Satellite System, aregional navigation system or GNSS augmentation system (e.g., Navigationwith Indian Constellation (NAVIC), Japan's Quasi-Zenith Satellite System(QZSS), France's Doppler Orbitography and Radio-positioning Integratedby Satellite (DORIS), etc.), or the like. The positioning circuitry 645comprises various hardware elements (e.g., including hardware devicessuch as switches, filters, amplifiers, antenna elements, and the like tofacilitate OTA communications) to communicate with components of apositioning network, such as navigation satellite constellation nodes.In some embodiments, the positioning circuitry 645 can include aMicro-Technology for Positioning, Navigation, and Timing (Micro-PNT) ICthat uses a master timing clock to perform position tracking/estimationwithout GNSS assistance. The positioning circuitry 645 may also be partof, or interact with, the baseband circuitry 610 and/or RFEMs 615 tocommunicate with the nodes and components of the positioning network.The positioning circuitry 645 may also provide position data and/or timedata to the application circuitry 605, which may use the data tosynchronize operations with various infrastructure (e.g., RAN nodes 311,etc.), or the like.

The components illustrated in FIG. 6 communicate with one another usinginterface circuitry, which can include any number of bus and/orinterconnect (IX) technologies such as industry standard architecture(ISA), extended ISA (EISA), peripheral component interconnect (PCI),peripheral component interconnect extended (PCIx), PCI express (PCIe),or any number of other technologies. The bus/IX may be a proprietarybus, for example, used in a System on Chip (SoC) based system. Otherbus/IX systems may be included, such as an I²C interface, an SPIinterface, point to point interfaces, and a power bus, among others.

FIG. 7 illustrates an example of a platform 700 (or “device 700”) inaccordance with various embodiments. In some embodiments, the computerplatform 700 may be suitable for use as UEs 301, 401, applicationservers 330, and/or any other element/device discussed herein. Theplatform 700 can include any combinations of the components shown in theexample. The components of platform 700 can be implemented as integratedcircuits (ICs), portions thereof, discrete electronic devices, or othermodules, logic, hardware, software, firmware, or a combination thereofadapted in the computer platform 700, or as components otherwiseincorporated within a chassis of a larger system. The block diagram ofFIG. 7 is intended to show a high level view of components of thecomputer platform 700. However, some of the components shown may beomitted, additional components may be present, and different arrangementof the components shown may occur in other implementations.

Application circuitry 705 includes circuitry such as, but not limited toone or more processors (or processor cores), cache memory, and one ormore of LDOs, interrupt controllers, serial interfaces such as SPI, I²Cor universal programmable serial interface module, RTC, timer-countersincluding interval and watchdog timers, general purpose I/O, memory cardcontrollers such as SD MMC or similar, USB interfaces, MIPI interfaces,and JTAG test access ports. The processors (or cores) of the applicationcircuitry 705 may be coupled with or can include memory/storage elementsand can be configured to execute instructions stored in thememory/storage to enable various applications or operating systems torun on the system 700. In some embodiments, the memory/storage elementsmay be on-chip memory circuitry, which can include any suitable volatileand/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flashmemory, solid-state memory, and/or any other type of memory devicetechnology, such as those discussed herein.

The processor(s) of application circuitry 705 can include, for example,one or more processor cores, one or more application processors, one ormore GPUs, one or more RISC processors, one or more ARM processors, oneor more CISC processors, one or more DSP, one or more FPGAs, one or morePLDs, one or more ASICs, one or more microprocessors or controllers, amultithreaded processor, an ultra-low voltage processor, an embeddedprocessor, some other known processing element, or any suitablecombination thereof. In some embodiments, the application circuitry 705may comprise, or may be, a special-purpose processor/controller tooperate according to the various embodiments herein.

As examples, the processor(s) of application circuitry 705 can includean Intel® Architecture Core™ based processor, such as a Quark™, anAtom™, an i3, an i5, an i7, or an MCU-class processor, or another suchprocessor available from Intel® Corporation, Santa Clara, Calif. Theprocessors of the application circuitry 705 may also be one or more ofAdvanced Micro Devices (AMD) Ryzen® processor(s) or AcceleratedProcessing Units (APUs); A5-A9 processor(s) from Apple® Inc.,Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., TexasInstruments, Inc.® Open Multimedia Applications Platform (OMAP)™processor(s); a MIPS-based design from MIPS Technologies, Inc. such asMIPS Warrior M-class, Warrior I-class, and Warrior P-class processors;an ARM-based design licensed from ARM Holdings, Ltd., such as the ARMCortex-A, Cortex-R, and Cortex-M family of processors; or the like. Insome embodiments, the application circuitry 705 may be a part of asystem on a chip (SoC) in which the application circuitry 705 and othercomponents are formed into a single integrated circuit, or a singlepackage, such as the Edison™ or Galileo™ SoC boards from Intel®Corporation.

Additionally or alternatively, application circuitry 705 can includecircuitry such as, but not limited to, one or more a field-programmabledevices (FPDs) such as FPGAs and the like; programmable logic devices(PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), andthe like; ASICs such as structured ASICs and the like; programmable SoCs(PSoCs); and the like. In such embodiments, the circuitry of applicationcircuitry 705 may comprise logic blocks or logic fabric, and otherinterconnected resources that may be programmed to perform variousfunctions, such as the procedures, methods, functions, etc. of thevarious embodiments discussed herein. In such embodiments, the circuitryof application circuitry 705 can include memory cells (e.g., erasableprogrammable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), flash memory, static memory(e.g., static random access memory (SRAM), anti-fuses, etc.)) used tostore logic blocks, logic fabric, data, etc. in look-up tables (LUTs)and the like.

The baseband circuitry 705 can be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Thevarious hardware electronic elements of baseband circuitry 705 arediscussed infra with regard to FIG. 8.

The RFEMs 715 may comprise a millimeter wave (mmWave) RFEM and one ormore sub-mmWave radio frequency integrated circuits (RFICs). In someembodiments, the one or more sub-mmWave RFICs may be physicallyseparated from the mmWave RFEM. The RFICs can include connections to oneor more antennas or antenna arrays (see e.g., antenna array 811 of FIG.8 infra), and the RFEM may be connected to multiple antennas. Inalternative implementations, both mmWave and sub-mmWave radio functionscan be implemented in the same physical RFEM 715, which incorporatesboth mmWave antennas and sub-mmWave.

The memory circuitry 720 can include any number and type of memorydevices used to provide for a given amount of system memory. Asexamples, the memory circuitry 720 can include one or more of volatilememory including random access memory (RAM), dynamic RAM (DRAM) and/orsynchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), magnetoresistiverandom access memory (MRAM), etc. The memory circuitry 720 may bedeveloped in accordance with a Joint Electron Devices EngineeringCouncil (JEDEC) low power double data rate (LPDDR)-based design, such asLPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry 720 can beimplemented as one or more of solder down packaged integrated circuits,single die package (SDP), dual die package (DDP) or quad die package(Q17P), socketed memory modules, dual inline memory modules (DIMMs)including microDIMMs or MiniDIMMs, and/or soldered onto a motherboardvia a ball grid array (BGA). In low power implementations, the memorycircuitry 720 may be on-die memory or registers associated with theapplication circuitry 705. To provide for persistent storage ofinformation such as data, applications, operating systems and so forth,memory circuitry 720 can include one or more mass storage devices, whichcan include, inter alia, a solid state disk drive (SSDD), hard diskdrive (HDD), a micro HDD, resistance change memories, phase changememories, holographic memories, or chemical memories, among others. Forexample, the computer platform 700 may incorporate the three-dimensional(3D) cross-point (XPOINT) memories from Intel® and Micron®.

Removable memory circuitry 723 can include devices, circuitry,enclosures/housings, ports or receptacles, etc. used to couple portabledata storage devices with the platform 700. These portable data storagedevices may be used for mass storage purposes, and can include, forexample, flash memory cards (e.g., Secure Digital (SD) cards, microSDcards, xD picture cards, and the like), and USB flash drives, opticaldiscs, external HDDs, and the like.

The platform 700 can also include interface circuitry (not shown) thatis used to connect external devices with the platform 700. The externaldevices connected to the platform 700 via the interface circuitryinclude sensor circuitry 721 and electro-mechanical components (EMCs)722, as well as removable memory devices coupled to removable memorycircuitry 723.

The sensor circuitry 721 includes devices, modules, or subsystems whosepurpose is to detect events or changes in its environment and send theinformation (sensor data) about the detected events to some other adevice, module, subsystem, etc. Examples of such sensors include, interalia, inertia measurement units (IMUs) comprising accelerometers,gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS)or nanoelectromechanical systems (NEMS) comprising 3-axisaccelerometers, 3-axis gyroscopes, and/or magnetometers; level sensors;flow sensors; temperature sensors (e.g., thermistors); pressure sensors;barometric pressure sensors; gravimeters; altimeters; image capturedevices (e.g., cameras or lensless apertures); light detection andranging (LiDAR) sensors; proximity sensors (e.g., infrared radiationdetector and the like), depth sensors, ambient light sensors, ultrasonictransceivers; microphones or other like audio capture devices; etc.

EMCs 722 include devices, modules, or subsystems whose purpose is toenable platform 700 to change its state, position, and/or orientation,or move or control a mechanism or (sub)system. Additionally, EMCs 722can be configured to generate and send messages/signalling to othercomponents of the platform 700 to indicate a current state of the EMCs722. Examples of the EMCs 722 include one or more power switches, relaysincluding electromechanical relays (EMRs) and/or solid state relays(SSRs), actuators (e.g., valve actuators, etc.), an audible soundgenerator, a visual warning device, motors (e.g., DC motors, steppermotors, etc.), wheels, thrusters, propellers, claws, clamps, hooks,and/or other like electro-mechanical components. In some embodiments,platform 700 is configured to operate one or more EMCs 722 based on oneor more captured events and/or instructions or control signals receivedfrom a service provider and/or various clients.

In some embodiments, the interface circuitry connects the platform 700with positioning circuitry 745. The positioning circuitry 745 includescircuitry to receive and decode signals transmitted/broadcasted by apositioning network of a GNSS. Examples of navigation satelliteconstellations (or GNSS) include United States' GPS, Russia's GLONASS,the European Union's Galileo system, China's BeiDou Navigation SatelliteSystem, a regional navigation system or GNSS augmentation system (e.g.,NAVIC), Japan's QZSS, France's DORIS, etc.), or the like. Thepositioning circuitry 745 comprises various hardware elements (e.g.,including hardware devices such as switches, filters, amplifiers,antenna elements, and the like to facilitate OTA communications) tocommunicate with components of a positioning network, such as navigationsatellite constellation nodes. In some embodiments, the positioningcircuitry 745 can include a Micro-PNT IC that uses a master timing clockto perform position tracking/estimation without GNSS assistance. Thepositioning circuitry 745 may also be part of, or interact with, thebaseband circuitry 705 and/or RFEMs 715 to communicate with the nodesand components of the positioning network. The positioning circuitry 745may also provide position data and/or time data to the applicationcircuitry 705, which may use the data to synchronize operations withvarious infrastructure (e.g., radio base stations), for turn-by-turnnavigation applications, or the like

In some embodiments, the interface circuitry connects the platform 700with Near-Field Communication (NFC) circuitry 740. NFC circuitry 740 isconfigured to provide contactless, short-range communications based onradio frequency identification (RFID) standards, wherein magnetic fieldinduction is used to enable communication between NFC circuitry 740 andNFC-enabled devices external to the platform 700 (e.g., an “NFCtouchpoint”). NFC circuitry 740 comprises an NFC controller coupled withan antenna element and a processor coupled with the NFC controller. TheNFC controller may be a chip/IC providing NFC functionalities to the NFCcircuitry 740 by executing NFC controller firmware and an NFC stack. TheNFC stack may be executed by the processor to control the NFCcontroller, and the NFC controller firmware may be executed by the NFCcontroller to control the antenna element to emit short-range RFsignals. The RF signals may power a passive NFC tag (e.g., a microchipembedded in a sticker or wristband) to transmit stored data to the NFCcircuitry 740, or initiate data transfer between the NFC circuitry 740and another active NFC device (e.g., a smartphone or an NFC-enabled POSterminal) that is proximate to the platform 700.

The driver circuitry 746 can include software and hardware elements thatoperate to control particular devices that are embedded in the platform700, attached to the platform 700, or otherwise communicatively coupledwith the platform 700. The driver circuitry 746 can include individualdrivers allowing other components of the platform 700 to interact withor control various input/output (I/O) devices that may be presentwithin, or connected to, the platform 700. For example, driver circuitry746 can include a display driver to control and allow access to adisplay device, a touchscreen driver to control and allow access to atouchscreen interface of the platform 700, sensor drivers to obtainsensor readings of sensor circuitry 721 and control and allow access tosensor circuitry 721, EMC drivers to obtain actuator positions of theEMCs 722 and/or control and allow access to the EMCs 722, a cameradriver to control and allow access to an embedded image capture device,audio drivers to control and allow access to one or more audio devices.

The power management integrated circuitry (PMIC) 725 (also referred toas “power management circuitry 725”) may manage power provided tovarious components of the platform 700. In particular, with respect tothe baseband circuitry 705, the PMIC 725 may control power-sourceselection, voltage scaling, battery charging, or DC-to-DC conversion.The PMIC 725 may often be included when the platform 700 is capable ofbeing powered by a battery 730, for example, when the device is includedin a UE 301, 301.

In some embodiments, the PMIC 725 may control, or otherwise be part of,various power saving mechanisms of the platform 700. For example, if theplatform 700 is in an RRC_Connected state, where it is still connectedto the RAN node as it expects to receive traffic shortly, then it mayenter a state known as Discontinuous Reception Mode (DRX) after a periodof inactivity. During this state, the platform 700 may power down forbrief intervals of time and thus save power. If there is no data trafficactivity for an extended period of time, then the platform 700 maytransition off to an RRC_Idle state, where it disconnects from thenetwork and does not perform operations such as channel qualityfeedback, handover, etc. The platform 700 goes into a very low powerstate and it performs paging where again it periodically wakes up tolisten to the network and then powers down again. The platform 700 maynot receive data in this state; in order to receive data, it musttransition back to RRC_Connected state. An additional power saving modemay allow a device to be unavailable to the network for periods longerthan a paging interval (ranging from seconds to a few hours). Duringthis time, the device is totally unreachable to the network and maypower down completely. Any data sent during this time incurs a largedelay and it is assumed the delay is acceptable.

A battery 730 may power the platform 700, although in some examples theplatform 700 may be mounted deployed in a fixed location, and may have apower supply coupled to an electrical grid. The battery 730 may be alithium ion battery, a metal-air battery, such as a zinc-air battery, analuminum-air battery, a lithium-air battery, and the like. In someembodiments, such as in V2X applications, the battery 730 may be atypical lead-acid automotive battery.

In some embodiments, the battery 730 can be a “smart battery,” whichincludes or is coupled with a Battery Management System (BMS) or batterymonitoring integrated circuitry. The BMS may be included in the platform700 to track the state of charge (SoCh) of the battery 730. The BMS maybe used to monitor other parameters of the battery 730 to providefailure predictions, such as the state of health (SoH) and the state offunction (SoF) of the battery 730. The BMS communicate the informationof the battery 730 to the application circuitry 705 or other componentsof the platform 700. The BMS may also include an analog-to-digital (ADC)convertor that allows the application circuitry 705 to directly monitorthe voltage of the battery 730 or the current flow from the battery 730.The battery parameters may be used to determine actions that theplatform 700 may perform, such as transmission frequency, networkoperation, sensing frequency, and the like.

A power block, or other power supply coupled to an electrical grid canbe coupled with the BMS to charge the battery 730. In some examples, thepower block XS30 may be replaced with a wireless power receiver toobtain the power wirelessly, for example, through a loop antenna in thecomputer platform 700. In these examples, a wireless battery chargingcircuit may be included in the BMS. The specific charging circuitschosen may depend on the size of the battery 730, and thus, the currentrequired. The charging may be performed using the Airfuel standardpromulgated by the Airfuel Alliance, the Qi wireless charging standardpromulgated by the Wireless Power Consortium, or the Rezence chargingstandard promulgated by the Alliance for Wireless Power, among others.

User interface circuitry 750 includes various input/output (I/O) devicespresent within, or connected to, the platform 700, and includes one ormore user interfaces designed to enable user interaction with theplatform 700 and/or peripheral component interfaces designed to enableperipheral component interaction with the platform 700. The userinterface circuitry 750 includes input device circuitry and outputdevice circuitry. Input device circuitry includes any physical orvirtual means for accepting an input including, inter alia, one or morephysical or virtual buttons (e.g., a reset button), a physical keyboard,keypad, mouse, touchpad, touchscreen, microphones, scanner, headset,and/or the like. The output device circuitry includes any physical orvirtual means for showing information or otherwise conveyinginformation, such as sensor readings, actuator position(s), or otherlike information. Output device circuitry can include any number and/orcombinations of audio or visual display, including, inter alia, one ormore simple visual outputs/indicators (e.g., binary status indicators(e.g., light emitting diodes (LEDs)) and multi-character visual outputs,or more complex outputs such as display devices or touchscreens (e.g.,Liquid Chrystal Displays (LCD), LED displays, quantum dot displays,projectors, etc.), with the output of characters, graphics, multimediaobjects, and the like being generated or produced from the operation ofthe platform 700. The output device circuitry may also include speakersor other audio emitting devices, printer(s), and/or the like. In someembodiments, the sensor circuitry 721 may be used as the input devicecircuitry (e.g., an image capture device, motion capture device, or thelike) and one or more EMCs may be used as the output device circuitry(e.g., an actuator to provide haptic feedback or the like). In anotherexample, NFC circuitry comprising an NFC controller coupled with anantenna element and a processing device may be included to readelectronic tags and/or connect with another NFC-enabled device.Peripheral component interfaces can include, but are not limited to, anon-volatile memory port, a USB port, an audio jack, a power supplyinterface, etc.

Although not shown, the components of platform 700 communicate with oneanother using a suitable bus or interconnect (IX) technology, which caninclude any number of technologies, including ISA, EISA, PCI, PCIx,PCIe, a Time-Trigger Protocol (TTP) system, a FlexRay system, or anynumber of other technologies. The bus/IX may be a proprietary bus/IX,for example, used in a SoC based system. Other bus/IX systems may beincluded, such as an I²C interface, an SPI interface, point-to-pointinterfaces, and a power bus, among others.

Exemplary Baseband Circuitry and Radio Front End Modules

FIG. 8 illustrates example components of baseband circuitry 810 andradio front end modules (RFEMs) 815 in accordance with variousembodiments. The baseband circuitry 810 corresponds to the basebandcircuitry 610 and 705 of FIG. 6 and FIG. 7, respectively. The RFEM 815corresponds to the RFEM 615 and 715 of FIG. 6 and FIG. 7, respectively.As shown, the RFEMs 815 can include Radio Frequency (RF) circuitry 806,front-end module (FEM) circuitry 808, antenna array 811 coupled togetherat least as shown.

The baseband circuitry 810 includes circuitry and/or control logicconfigured to carry out various radio/network protocol and radio controlfunctions that enable communication with one or more radio networks viathe RF circuitry 806. The radio control functions can include, but arenot limited to, signal modulation/demodulation, encoding/decoding, radiofrequency shifting, etc. In some embodiments, modulation/demodulationcircuitry of the baseband circuitry 810 can include Fast-FourierTransform (FFT), precoding, or constellation mapping/demappingfunctionality. In some embodiments, encoding/decoding circuitry of thebaseband circuitry 810 can include convolution, tail-biting convolution,turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoderfunctionality. Embodiments of modulation/demodulation andencoder/decoder functionality are not limited to these examples and caninclude other suitable functionality in other embodiments. The basebandcircuitry 810 is configured to process baseband signals received from areceive signal path of the RF circuitry 806 and to generate basebandsignals for a transmit signal path of the RF circuitry 806. The basebandcircuitry 810 is configured to interface with application circuitry605/705 (see, FIG. 6 and FIG. 7) for generation and processing of thebaseband signals and for controlling operations of the RF circuitry 806.The baseband circuitry 810 handles various radio control functions.

The aforementioned circuitry and/or control logic of the basebandcircuitry 810 can include one or more single or multi-core processors.For example, the one or more processors can include a 3G basebandprocessor 804A, a 4G/LTE baseband processor 804B, a 5G/NR basebandprocessor 804C, or some other baseband processor(s) 804D for otherexisting generations, generations in development or to be developed inthe future (e.g., sixth generation (6G), etc.). In other embodiments,some or all of the functionality of baseband processors 804A-D may beincluded in modules stored in the memory 804G and executed via a CentralProcessing Unit (CPU) 804E. In other embodiments, some or all of thefunctionality of baseband processors 804A-D may be provided as hardwareaccelerators (e.g., FPGAs, ASICs, etc.) loaded with the appropriate bitstreams or logic blocks stored in respective memory cells. In variousembodiments, the memory 804G stores program code of a real-time OS(RTOS), which when executed by the CPU 804E (or other basebandprocessor), is to cause the CPU 804E (or other baseband processor) tomanage resources of the baseband circuitry 810, schedule tasks, etc.Examples of the RTOS can include Operating System Embedded (OSE)™provided by Enea®, Nucleus RTOS™ provided by Mentor Graphics®, VersatileReal-Time Executive (VRTX) provided by Mentor Graphics®, ThreadX™provided by Express Logic®, FreeRTOS, REX OS provided by Qualcomm®, OKL4provided by Open Kernel (OK) Labs®, or any other suitable RTOS, such asthose discussed herein. In addition, the baseband circuitry 810 includesone or more audio digital signal processor(s) (DSP) 804F. The audioDSP(s) 804F include elements for compression/decompression and echocancellation and can include other suitable processing elements in otherembodiments.

In some embodiments, each of the processors 804A-804E include respectivememory interfaces to send/receive data to/from the memory 804G. Thebaseband circuitry 810 may further include one or more interfaces tocommunicatively couple to other circuitries/devices, such as aninterface to send/receive data to/from memory external to the basebandcircuitry 810; an application circuitry interface to send/receive datato/from the application circuitry 605/705 of FIGS. 10-XT); an RFcircuitry interface to send/receive data to/from RF circuitry 806 ofFIG. 8; a wireless hardware connectivity interface to send/receive datato/from one or more wireless hardware elements (e.g., Near FieldCommunication (NFC) components, Bluetooth®/Bluetooth® Low Energycomponents, Wi-Fi® components, and/or the like); and a power managementinterface to send/receive power or control signals to/from the PMIC 725.

In alternate embodiments (which may be combined with the above describedembodiments), baseband circuitry 810 comprises one or more digitalbaseband systems, which are coupled with one another via an interconnectsubsystem and to a CPU subsystem, an audio subsystem, and an interfacesubsystem. The digital baseband subsystems may also be coupled to adigital baseband interface and a mixed-signal baseband subsystem viaanother interconnect subsystem. Each of the interconnect subsystems caninclude a bus system, point-to-point connections, network-on-chip (NOC)structures, and/or some other suitable bus or interconnect technology,such as those discussed herein. The audio subsystem can include DSPcircuitry, buffer memory, program memory, speech processing acceleratorcircuitry, data converter circuitry such as analog-to-digital anddigital-to-analog converter circuitry, analog circuitry including one ormore of amplifiers and filters, and/or other like components. In anaspect of the present disclosure, baseband circuitry 810 can includeprotocol processing circuitry with one or more instances of controlcircuitry (not shown) to provide control functions for the digitalbaseband circuitry and/or radio frequency circuitry (e.g., the radiofront end modules 815).

Although not illustrated in FIG. 8, in some embodiments, the basebandcircuitry 810 includes individual processing device(s) to operate one ormore wireless communication protocols (e.g., a “multi-protocol basebandprocessor” or “protocol processing circuitry”) and individual processingdevice(s) to implement PHY layer functions. In these embodiments, thePHY layer functions include the aforementioned radio control functions.In these embodiments, the protocol processing circuitry operates orimplements various protocol layers/entities of one or more wirelesscommunication protocols. In a first example, the protocol processingcircuitry may operate LTE protocol entities and/or 5G/NR protocolentities when the baseband circuitry 810 and/or RF circuitry 806 arepart of mmWave communication circuitry or some other suitable cellularcommunication circuitry. In the first example, the protocol processingcircuitry would operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. Ina second example, the protocol processing circuitry may operate one ormore IEEE-based protocols when the baseband circuitry 810 and/or RFcircuitry 806 are part of a Wi-Fi communication system. In the secondexample, the protocol processing circuitry would operate Wi-Fi MAC andlogical link control (LLC) functions. The protocol processing circuitrycan include one or more memory structures (e.g., 804G) to store programcode and data for operating the protocol functions, as well as one ormore processing cores to execute the program code and perform variousoperations using the data. The baseband circuitry 810 may also supportradio communications for more than one wireless protocol.

The various hardware elements of the baseband circuitry 810 discussedherein can be implemented, for example, as a solder-down substrateincluding one or more integrated circuits (ICs), a single packaged ICsoldered to a main circuit board or a multi-chip module containing twoor more ICs. In one example, the components of the baseband circuitry810 may be suitably combined in a single chip or chipset, or disposed ona same circuit board. In another example, some or all of the constituentcomponents of the baseband circuitry 810 and RF circuitry 806 can beimplemented together such as, for example, a system on a chip (SoC) orSystem-in-Package (SiP). In another example, some or all of theconstituent components of the baseband circuitry 810 can be implementedas a separate SoC that is communicatively coupled with and RF circuitry806 (or multiple instances of RF circuitry 806). In yet another example,some or all of the constituent components of the baseband circuitry 810and the application circuitry 605/705 can be implemented together asindividual SoCs mounted to a same circuit board (e.g., a “multi-chippackage”).

In some embodiments, the baseband circuitry 810 provides forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, the baseband circuitry 810 supportscommunication with an E-UTRAN or other WMAN, a WLAN, a WPAN. Embodimentsin which the baseband circuitry 810 is configured to support radiocommunications of more than one wireless protocol may be referred to asmulti-mode baseband circuitry.

RF circuitry 806 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 806 can include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. RF circuitry 806 can include a receive signal path, which caninclude circuitry to down-convert RF signals received from the FEMcircuitry 808 and provide baseband signals to the baseband circuitry810. RF circuitry 806 may also include a transmit signal path, which caninclude circuitry to up-convert baseband signals provided by thebaseband circuitry 810 and provide RF output signals to the FEMcircuitry 808 for transmission.

In some embodiments, the receive signal path of the RF circuitry 806 caninclude mixer circuitry 806A, amplifier circuitry 806B and filtercircuitry 806C. In some embodiments, the transmit signal path of the RFcircuitry 806 can include filter circuitry 806C and mixer circuitry806A. RF circuitry 806 may also include synthesizer circuitry 806D forsynthesizing a frequency for use by the mixer circuitry 806A of thereceive signal path and the transmit signal path. In some embodiments,the mixer circuitry 806A of the receive signal path can be configured todown-convert RF signals received from the FEM circuitry 808 based on thesynthesized frequency provided by synthesizer circuitry 806D. Theamplifier circuitry 806B can be configured to amplify the down-convertedsignals and the filter circuitry 806C may be a low-pass filter (LPF) orband-pass filter (BPF) configured to remove unwanted signals from thedown-converted signals to generate output baseband signals. Outputbaseband signals may be provided to the baseband circuitry 810 forfurther processing. In some embodiments, the output baseband signals maybe zero-frequency baseband signals, although this is not a requirement.In some embodiments, mixer circuitry 806A of the receive signal path maycomprise passive mixers, although the scope of the embodiments is notlimited in this respect.

In some embodiments, the mixer circuitry 806A of the transmit signalpath can be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 806D togenerate RF output signals for the FEM circuitry 808. The basebandsignals may be provided by the baseband circuitry 810 and may befiltered by filter circuitry 806C.

In some embodiments, the mixer circuitry 806A of the receive signal pathand the mixer circuitry 806A of the transmit signal path can include twoor more mixers and may be arranged for quadrature downconversion andupconversion, respectively. In some embodiments, the mixer circuitry806A of the receive signal path and the mixer circuitry 806A of thetransmit signal path can include two or more mixers and may be arrangedfor image rejection (e.g., Hartley image rejection). In someembodiments, the mixer circuitry 806A of the receive signal path and themixer circuitry 806A of the transmit signal path may be arranged fordirect downconversion and direct upconversion, respectively. In someembodiments, the mixer circuitry 806A of the receive signal path and themixer circuitry 806A of the transmit signal path can be configured forsuper-heterodyne operation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, the RFcircuitry 806 can include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry and the baseband circuitry810 can include a digital baseband interface to communicate with the RFcircuitry 806.

In some dual-mode embodiments, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 806D may be afractional-N synthesizer or a fractional N/N+1 synthesizer, although thescope of the embodiments is not limited in this respect as other typesof frequency synthesizers may be suitable. For example, synthesizercircuitry 806D may be a delta-sigma synthesizer, a frequency multiplier,or a synthesizer comprising a phase-locked loop with a frequencydivider.

The synthesizer circuitry 806D can be configured to synthesize an outputfrequency for use by the mixer circuitry 806A of the RF circuitry 806based on a frequency input and a divider control input. In someembodiments, the synthesizer circuitry 806D may be a fractional N/N+1synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 810 orthe application circuitry 605/705 depending on the desired outputfrequency. In some embodiments, a divider control input (e.g., N) may bedetermined from a look-up table based on a channel indicated by theapplication circuitry 605/705.

Synthesizer circuitry 806D of the RF circuitry 806 can include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some embodiments, the divider may be a dual modulusdivider (DMD) and the phase accumulator may be a digital phaseaccumulator (DPA). In some embodiments, the DMD can be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example embodiments, theDLL can include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump and a D-type flip-flop. In these embodiments,the delay elements can be configured to break a VCO period up into Ndequal packets of phase, where Nd is the number of delay elements in thedelay line. In this way, the DLL provides negative feedback to helpensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 806D can be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someembodiments, the output frequency may be a LO frequency (fLO). In someembodiments, the RF circuitry 806 can include an IQ/polar converter.

FEM circuitry 808 can include a receive signal path, which can includecircuitry configured to operate on RF signals received from antennaarray 811, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 806 for furtherprocessing. FEM circuitry 808 may also include a transmit signal path,which can include circuitry configured to amplify signals fortransmission provided by the RF circuitry 806 for transmission by one ormore of antenna elements of antenna array 811. In various embodiments,the amplification through the transmit or receive signal paths may bedone solely in the RF circuitry 806, solely in the FEM circuitry 808, orin both the RF circuitry 806 and the FEM circuitry 808.

In some embodiments, the FEM circuitry 808 can include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry 808 can include a receive signal path and a transmit signalpath. The receive signal path of the FEM circuitry 808 can include anLNA to amplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 806). The transmitsignal path of the FEM circuitry 808 can include a power amplifier (PA)to amplify input RF signals (e.g., provided by RF circuitry 806), andone or more filters to generate RF signals for subsequent transmissionby one or more antenna elements of the antenna array 811.

The antenna array 811 comprises one or more antenna elements, each ofwhich is configured convert electrical signals into radio waves totravel through the air and to convert received radio waves intoelectrical signals. For example, digital baseband signals provided bythe baseband circuitry 810 is converted into analog RF signals (e.g.,modulated waveform) that can be amplified and transmitted via theantenna elements of the antenna array 811 including one or more antennaelements (not shown). The antenna elements may be omnidirectional,direction, or a combination thereof. The antenna elements may be formedin a multitude of arranges as are known and/or discussed herein. Theantenna array 811 may comprise microstrip antennas or printed antennasthat are fabricated on the surface of one or more printed circuitboards. The antenna array 811 may be formed in as a patch of metal foil(e.g., a patch antenna) in a variety of shapes, and may be coupled withthe RF circuitry 806 and/or FEM circuitry 808 using metal transmissionlines or the like.

Exemplary Protocol Functions that can be Implemented in a WirelessCommunication Device

Processors of the application circuitry 605/705 and processors of thebaseband circuitry 810 may be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 810, alone or in combination, may be used execute Layer 3,Layer 2, or Layer 1 functionality, while processors of the applicationcircuitry 605/705 may utilize data (e.g., packet data) received fromthese layers and further execute Layer 4 functionality (e.g.,Transmission Communication Protocol (TCP) and User Datagram Protocol(UDP) layers). As referred to herein, Layer 3 may comprise a RadioResource Control (RRC) layer, described in further detail below. Asreferred to herein, Layer 2 may comprise a Medium Access Control (MAC)layer, an Radio Link Control, (RLC) layer, and a Packet Data ConvergenceProtocol (PDCP) layer, described in further detail below. As referred toherein, Layer 1 may comprise a Physical (PHY) layer of a UE/RAN node,described in further detail below.

FIG. 9 illustrates various protocol functions that can be implemented ina wireless communication device in accordance with various embodiments.In particular, FIG. 9 includes an arrangement 900 showinginterconnections between various protocol layers/entities. The followingdescription of FIG. 9 is provided for various protocol layers/entitiesthat operate in conjunction with the 5G/NR system standards and LTEsystem standards, but some or all of the aspects of FIG. 9 may beapplicable to other wireless communication network systems as well.

The protocol layers of arrangement 900 can include one or more of PHY910, MAC 920, RLC 930, PDCP 940, SDAP 947, RRC 955, and NAS layer 957,in addition to other higher layer functions not illustrated. Theprotocol layers can include one or more service access points (e.g.,items 959, 956, 1750, 949, 945, 935, 925, and 915 in FIG. 9) thatprovides communication between two or more protocol layers.

The PHY 910 transmits and receives physical layer signals 910 that maybe received from or transmitted to one or more other communicationdevices. The PHY 910 may comprise one or more physical channels, such asthose discussed herein. The PHY 910 may further perform link adaptationor adaptive modulation and coding (AMC), power control, cell search(e.g., for initial synchronization and handover purposes), and othermeasurements used by higher layers, such as the RRC 955. The PHY 910 maystill further perform error detection on the transport channels, forwarderror correction (FEC) coding/decoding of the transport channels,modulation/demodulation of physical channels, interleaving, ratematching, mapping onto physical channels, and MIMO antenna processing.In some embodiments, an instance of PHY 910 may process requests fromand provide indications to an instance of MAC 920 via one or morePHY-SAP 915. According to some embodiments, requests and indicationscommunicated via PHY-SAP 915 may comprise one or more transportchannels.

Instance(s) of MAC 920 processes requests from, and provides indicationsto, an instance of RLC 930 via one or more MAC-SAPs 925. These requestsand indications communicated via the MAC-SAP 925 may comprise one ormore logical channels. The MAC 920 may perform mapping between thelogical channels and transport channels, multiplexing of MAC SDUs fromone or more logical channels onto TBs to be delivered to PHY 910 via thetransport channels, de-multiplexing MAC SDUs to one or more logicalchannels from TBs delivered from the PHY 910 via transport channels,multiplexing MAC SDUs onto TBs, scheduling information reporting, errorcorrection through HARQ, and logical channel prioritization.

Instance(s) of RLC 930 processes requests from and provides indicationsto an instance of PDCP 940 via one or more radio link control serviceaccess points (RLC-SAP) 935. These requests and indications communicatedvia RLC-SAP 935 may comprise one or more RLC channels. The RLC 930 mayoperate in a plurality of modes of operation, including: TransparentMode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC930 may execute transfer of upper layer protocol data units (PDUs),error correction through automatic repeat request (ARQ) for AM datatransfers, and concatenation, segmentation and reassembly of RLC SDUsfor UM and AM data transfers. The RLC 930 may also executere-segmentation of RLC data PDUs for AM data transfers, reorder RLC dataPDUs for UM and AM data transfers, detect duplicate data for UM and AMdata transfers, discard RLC SDUs for UM and AM data transfers, detectprotocol errors for AM data transfers, and perform RLC re-establishment.

Instance(s) of PDCP 940 processes requests from and provides indicationsto instance(s) of RRC 955 and/or instance(s) of SDAP 947 via one or morepacket data convergence protocol service access points (PDCP-SAP) 945.These requests and indications communicated via PDCP-SAP 945 maycomprise one or more radio bearers. The PDCP 940 may execute headercompression and decompression of IP data, maintain PDCP Sequence Numbers(SNs), perform in-sequence delivery of upper layer PDUs atre-establishment of lower layers, eliminate duplicates of lower layerSDUs at re-establishment of lower layers for radio bearers mapped on RLCAM, cipher and decipher control plane data, perform integrity protectionand integrity verification of control plane data, control timer-baseddiscard of data, and perform security operations (e.g., ciphering,deciphering, integrity protection, integrity verification, etc.).

Instance(s) of SDAP 947 processes requests from and provides indicationsto one or more higher layer protocol entities via one or more SDAP-SAP949. These requests and indications communicated via SDAP-SAP 949 maycomprise one or more QoS flows. The SDAP 947 may map QoS flows to DRBs,and vice versa, and may also mark QFIs in DL and UL packets. A singleSDAP entity 947 can be configured for an individual PDU session. In theUL direction, the NG-RAN 310 may control the mapping of QoS Flows toDRB(s) in two different ways, reflective mapping or explicit mapping.For reflective mapping, the SDAP 947 of a UE 301 may monitor the QFIs ofthe DL packets for each DRB, and may apply the same mapping for packetsflowing in the UL direction. For a DRB, the SDAP 947 of the UE 301 maymap the UL packets belonging to the QoS flows(s) corresponding to theQoS flow ID(s) and PDU session observed in the DL packets for that DRB.To enable reflective mapping, the NG-RAN 510 may mark DL packets overthe Uu interface with a QoS flow ID. The explicit mapping may involvethe RRC 955 configuring the SDAP 947 with an explicit QoS flow to DRBmapping rule, which may be stored and followed by the SDAP 947. In someembodiments, the SDAP 947 may only be used in NR implementations and maynot be used in LTE implementations.

The RRC 955 configures, via one or more management service access points(M-SAP), aspects of one or more protocol layers, which can include oneor more instances of PHY 910, MAC 920, RLC 930, PDCP 940 and SDAP 947.In some embodiments, an instance of RRC 955 may process requests fromand provide indications to one or more NAS entities 957 via one or moreRRC-SAPs 956. The main services and functions of the RRC 955 can includebroadcast of system information (e.g., included in MIBs or SIBs relatedto the NAS), broadcast of system information related to the accessstratum (AS), paging, establishment, maintenance and release of an RRCconnection between the UE 301 and RAN 310 (e.g., RRC connection paging,RRC connection establishment, RRC connection modification, and RRCconnection release), establishment, configuration, maintenance andrelease of point to point Radio Bearers, security functions includingkey management, inter-RAT mobility, and measurement configuration for UEmeasurement reporting. The MIBs and SIBs may comprise one or more IEs,which may each comprise individual data fields or data structures.

The NAS 957 forms the highest stratum of the control plane between theUE 301 and the AMF 521. The NAS 957 supports the mobility of the UEs 301and the session management procedures to establish and maintain IPconnectivity between the UE 301 and a P-GW in LTE systems.

In accordance with various embodiments, one or more protocol entities ofarrangement 900 can be implemented in UEs 301, RAN nodes 311, AMF 521 inNR implementations or MME 421 in LTE implementations, UPF 502 in NRimplementations or S-GW 422 and P-GW 423 in LTE implementations, or thelike to be used for control plane or user plane communications protocolstack between the aforementioned devices. In such embodiments, one ormore protocol entities that can be implemented in one or more of UE 301,gNB 311, AMF 521, etc. communicate with a respective peer protocolentity that can be implemented in or on another device using theservices of respective lower layer protocol entities to perform suchcommunication. In some embodiments, a gNB-CU of the gNB 311 may host theRRC 955, SDAP 947, and PDCP 940 of the gNB that controls the operationof one or more gNB-DUs, and the gNB-DUs of the gNB 311 may each host theRLC 930, MAC 920, and PHY 1310 of the gNB 311.

In a first example, a control plane protocol stack may comprise, inorder from highest layer to lowest layer, NAS 1357, RRC 1355, PDCP 940,RLC 930, MAC 1320, and PHY 1310. In this example, upper layers 960 maybe built on top of the NAS 1357, which includes an IP layer 961, an SCTP962, and an application layer signaling protocol (AP) 963.

In NR implementations, the AP 963 may be an NG application protocollayer (NGAP or NG-AP) 963 for the NG interface 313 defined between theNG-RAN node 311 and the AMF 521, or the AP 963 may be an Xn applicationprotocol layer (XnAP or Xn-AP) 963 for the Xn interface 212 that isdefined between two or more RAN nodes 311.

The NG-AP 963 supports the functions of the NG interface 313 and maycomprise Elementary Procedures (EPs). An NG-AP EP may be a unit ofinteraction between the NG-RAN node 311 and the AMF 521. The NG-AP 963services may comprise two groups: UE-associated services (e.g., servicesrelated to a UE 301) and non-UE-associated services (e.g., servicesrelated to the whole NG interface instance between the NG-RAN node 311and AMF 521). These services can include functions including, but notlimited to: a paging function for the sending of paging requests toNG-RAN nodes 311 involved in a particular paging area; a UE contextmanagement function for allowing the AMF 521 to establish, modify,and/or release a UE context in the AMF 521 and the NG-RAN node 311; amobility function for UEs 301 in ECM-CONNECTED mode for intra-system HOsto support mobility within NG-RAN and inter-system HOs to supportmobility from/to EPS systems; a NAS Signaling Transport function fortransporting or rerouting NAS messages between UE 301 and AMF 521; a NASnode selection function for determining an association between the AMF521 and the UE 301; NG interface management function(s) for setting upthe NG interface and monitoring for errors over the NG interface; awarning message transmission function for providing means to transferwarning messages via NG interface or cancel ongoing broadcast of warningmessages; a Configuration Transfer function for requesting andtransferring of RAN configuration information (e.g., SON information,performance measurement (PM) data, etc.) between two RAN nodes 311 viaCN 320; and/or other like functions.

The XnAP 963 supports the functions of the Xn interface 212 and maycomprise XnAP basic mobility procedures and XnAP global procedures. TheXnAP basic mobility procedures may comprise procedures used to handle UEmobility within the NG RAN 311 (or E-UTRAN 310), such as handoverpreparation and cancellation procedures, SN Status Transfer procedures,UE context retrieval and UE context release procedures, RAN pagingprocedures, dual connectivity related procedures, and the like. The XnAPglobal procedures may comprise procedures that are not related to aspecific UE 301, such as Xn interface setup and reset procedures, NG-RANupdate procedures, cell activation procedures, and the like.

In LTE implementations, the AP 963 can be an S1 Application Protocollayer (S1-AP) 963 for the S1 interface 313 defined between an E-UTRANnode 311 and an MME, or the AP 963 may be an X2 application protocollayer (X2AP or X2-AP) 963 for the X2 interface 212 that is definedbetween two or more E-UTRAN nodes 311.

The S1 Application Protocol layer (S1-AP) 963 supports the functions ofthe S1 interface, and similar to the NG-AP discussed previously, theS1-AP may comprise S1-AP EPs. An S1-AP EP may be a unit of interactionbetween the E-UTRAN node 311 and an MME 421 within an LTE CN 320. TheS1-AP 963 services may comprise two groups: UE-associated services andnon UE-associated services. These services perform functions including,but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UEcapability indication, mobility, NAS signaling transport, RANInformation Management (RIM), and configuration transfer.

The X2AP 963 supports the functions of the X2 interface 212 and maycomprise X2AP basic mobility procedures and X2AP global procedures. TheX2AP basic mobility procedures may comprise procedures used to handle UEmobility within the E-UTRAN 320, such as handover preparation andcancellation procedures, SN Status Transfer procedures, UE contextretrieval and UE context release procedures, RAN paging procedures, dualconnectivity related procedures, and the like. The X2AP globalprocedures may comprise procedures that are not related to a specific UE301, such as X2 interface setup and reset procedures, load indicationprocedures, error indication procedures, cell activation procedures, andthe like.

The SCTP layer (alternatively referred to as the SCTP/IP layer) 962provides guaranteed delivery of application layer messages (e.g., NGAPor XnAP messages in NR implementations, or S1-AP or X2AP messages in LTEimplementations). The SCTP 962 may ensure reliable delivery of signalingmessages between the RAN node 311 and the AMF 521/MME 421 based, inpart, on the IP protocol, supported by the IP 961. The Internet Protocollayer (IP) 961 may be used to perform packet addressing and routingfunctionality. In some embodiments the IP layer 961 may usepoint-to-point transmission to deliver and convey PDUs. In this regard,the RAN node 311 may comprise L2 and L1 layer communication links (e.g.,wired or wireless) with the MME/AMF to exchange information.

In a second example, a user plane protocol stack may comprise, in orderfrom highest layer to lowest layer, SDAP 947, PDCP 940, RLC 930, MAC1320, and PHY 1310. The user plane protocol stack may be used forcommunication between the UE 301, the RAN node 311, and UPF 502 in NRimplementations or an S-GW 422 and P-GW 423 in LTE implementations. Inthis example, upper layers 951 may be built on top of the SDAP 947, andcan include a user datagram protocol (UDP) and IP security layer(UDP/IP) 952, a General Packet Radio Service (GPRS) Tunneling Protocolfor the user plane layer (GTP-U) 953, and a User Plane PDU layer (UPPDU) 963.

The transport network layer 954 (also referred to as a “transportlayer”) can be built on IP transport, and the GTP-U 953 may be used ontop of the UDP/IP layer 952 (comprising a UDP layer and IP layer) tocarry user plane PDUs (UP-PDUs). The IP layer (also referred to as the“Internet layer”) may be used to perform packet addressing and routingfunctionality. The IP layer may assign IP addresses to user data packetsin any of IPv4, IPv6, or PPP formats, for example.

The GTP-U 953 is be used for carrying user data within the GPRS corenetwork and between the radio access network and the core network. Theuser data transported can be packets in any of IPv4, IPv6, or PPPformats, for example. The UDP/IP 952 provides checksums for dataintegrity, port numbers for addressing different functions at the sourceand destination, and encryption and authentication on the selected dataflows. The RAN node 311 and the S-GW 422 may utilize an S1-U interfaceto exchange user plane data via a protocol stack comprising an L1 layer(e.g., PHY 910), an L2 layer (e.g., MAC 920, RLC 930, PDCP 940, and/orSDAP 947), the UDP/IP layer 952, and the GTP-U 953. The S-GW 422 and theP-GW 423 may utilize an S5/S8a interface to exchange user plane data viaa protocol stack comprising an L1 layer, an L2 layer, the UDP/IP layer952, and the GTP-U 953. As discussed previously, NAS protocols supportthe mobility of the UE 301 and the session management procedures toestablish and maintain IP connectivity between the UE 301 and the P-GW423.

Moreover, although not illustrated in FIG. 9, an application layer maybe present above the AP 963 and/or the transport network layer 954. Theapplication layer may be a layer in which a user of the UE 301, RAN node311, or other network element interacts with software applications beingexecuted, for example, by application circuitry 605 or applicationcircuitry 705, respectively. The application layer may also provide oneor more interfaces for software applications to interact withcommunications systems of the UE 301 or RAN node 311, such as thebaseband circuitry 810. In some embodiments the IP layer and/or theapplication layer provides the same or similar functionality as layers5-7, or portions thereof, of the Open Systems Interconnection (OSI)model (e.g., OSI Layer 7—the application layer, OSI Layer 6—thepresentation layer, and OSI Layer 5—the session layer).

FIG. 10 illustrates components of a core network in accordance withvarious embodiments. The components of the CN 420 can be implemented inone physical node or separate physical nodes including components toread and execute instructions from a machine-readable orcomputer-readable medium (e.g., a non-transitory machine-readablestorage medium). In some embodiments, the components of CN 520 can beimplemented in a same or similar manner as discussed herein with regardto the components of CN 420. In some embodiments, NFV is utilized tovirtualize any or all of the above-described network node functions viaexecutable instructions stored in one or more computer-readable storagemediums (described in further detail below). A logical instantiation ofthe CN 420 may be referred to as a network slice 1001, and individuallogical instantiations of the CN 420 provides specific networkcapabilities and network characteristics. A logical instantiation of aportion of the CN 420 may be referred to as a network sub-slice 1002(e.g., the network sub-slice 1002 is shown to include the P-GW 423 andthe PCRF 426).

As used herein, the terms “instantiate,” “instantiation,” and the likemay refer to the creation of an instance, and an “instance” may refer toa concrete occurrence of an object, which may occur, for example, duringexecution of program code. A network instance may refer to informationidentifying a domain, which may be used for traffic detection androuting in case of different IP domains or overlapping IP addresses. Anetwork slice instance may refer to a set of network functions (NFs)instances and the resources (e.g., compute, storage, and networkingresources) required to deploy the network slice.

With respect to 5G systems (see, for example, FIG. 5 above), a networkslice always comprises a Radio Access Network (RAN) part and a corenetwork (CN) part. The support of network slicing relies on theprinciple that traffic for different slices is handled by differentProtocol Data Unit (PDU) sessions. The network can realize the differentnetwork slices by scheduling and also by providing different L1/L2configurations. The UE 501 provides assistance information for networkslice selection in an appropriate Radio Resource Control (RRC) message,if it has been provided by NAS. While the network can support largenumber of slices, the UE need not support more than 8 slicessimultaneously.

A network slice can include the CN 520 control plane and user planeNetwork Functions (NFs), Next Generation Radio Access Networks (NG-RANs)510 in a serving PLMN, and a N3IWF functions in the serving PLMN.Individual network slices may have different S-NSSAI and/or may havedifferent SSTs. NSSAI includes one or more S-NSSAIs, and each networkslice is uniquely identified by an S-NSSAI. Network slices may differfor supported features and network functions optimizations, and/ormultiple network slice instances may deliver the same service/featuresbut for different groups of UEs 501 (e.g., enterprise users). Forexample, individual network slices may deliver different committedservice(s) and/or may be dedicated to a particular customer orenterprise. In this example, each network slice may have differentS-NSSAIs with the same SST but with different slice differentiators.Additionally, a single UE may be served with one or more network sliceinstances simultaneously via a 5G AN and associated with eight differentS-NSSAIs. Moreover, an AMF 521 instance serving an individual UE 501 maybelong to each of the network slice instances serving that UE.

Network Slicing in the NG-RAN 510 involves RAN slice awareness. RANslice awareness includes differentiated handling of traffic fordifferent network slices, which have been pre-configured. Sliceawareness in the NG-RAN 510 is introduced at the PDU session level byindicating the S-NSSAI corresponding to a PDU session in all signalingthat includes PDU session resource information. How the NG-RAN 510supports the slice enabling in terms of NG-RAN functions (e.g., the setof network functions that comprise each slice) is implementationdependent. The NG-RAN 510 selects the RAN part of the network sliceusing assistance information provided by the UE 501 or the 5GC 520,which unambiguously identifies one or more of the pre-configured networkslices in the PLMN. The NG-RAN 510 also supports resource management andpolicy enforcement between slices as per SLAs. A single NG-RAN nodesupports multiple slices, and the NG-RAN 510 may also apply anappropriate RRM policy for the SLA in place to each supported slice. TheNG-RAN 510 may also support QoS differentiation within a slice.

The NG-RAN 510 may also use the UE assistance information for theselection of an AMF 521 during an initial attach, if available. TheNG-RAN 510 uses the assistance information for routing the initial NASto an AMF 521. If the NG-RAN 510 is unable to select an AMF 521 usingthe assistance information, or the UE 501 does not provide any suchinformation, the NG-RAN 510 sends the NAS signaling to a default AMF521, which may be among a pool of AMFs 521. For subsequent accesses, theUE 501 provides a temp ID, which is assigned to the UE 501 by the 5GC520, to enable the NG-RAN 510 to route the NAS message to theappropriate AMF 521 as long as the temp ID is valid. The NG-RAN 510 isaware of, and can reach, the AMF 521 that is associated with the tempID. Otherwise, the method for initial attach applies.

The NG-RAN 510 supports resource isolation between slices. NG-RAN 510resource isolation may be achieved by means of RRM policies andprotection mechanisms that can avoid that shortage of shared resourcesif one slice breaks the service level agreement for another slice. Insome embodiments, it is possible to fully dedicate NG-RAN 510 resourcesto a certain slice. How NG-RAN 510 supports resource isolation isimplementation dependent.

Some slices may be available only in part of the network. Awareness inthe NG-RAN 510 of the slices supported in the cells of its neighbors maybe beneficial for inter-frequency mobility in connected mode. The sliceavailability may not change within the UE's registration area. TheNG-RAN 510 and the 5GC 520 are responsible to handle a service requestfor a slice that may or may not be available in a given area. Admissionor rejection of access to a slice may depend on factors such as supportfor the slice, availability of resources, support of the requestedservice by NG-RAN 510.

The UE 501 may be associated with multiple network slicessimultaneously. In case the UE 501 is associated with multiple slicessimultaneously, only one signaling connection is maintained, and forintra-frequency cell reselection, the UE 501 tries to camp on the bestcell. For inter-frequency cell reselection, dedicated priorities can beused to control the frequency on which the UE 501 camps. The 5GC 520 isto validate that the UE 501 has the rights to access a network slice.Prior to receiving an Initial Context Setup Request message, the NG-RAN510 may be allowed to apply some provisional/local policies, based onawareness of a particular slice that the UE 501 is requesting to access.During the initial context setup, the NG-RAN 510 is informed of theslice for which resources are being requested.

Network Functions Virtualization (NFV) architectures and infrastructuresmay be used to virtualize one or more NFs, alternatively performed byproprietary hardware, onto physical resources comprising a combinationof industry-standard server hardware, storage hardware, or switches. Inother words, NFV systems can be used to execute virtual orreconfigurable implementations of one or more EPC components/functions.

FIG. 11 is a block diagram illustrating components, according to someexample embodiments, of a system 1100 to support Network FunctionsVirtualization (NFV). The system 1100 is illustrated as including aVirtualized Infrastructure Manager (VIM) 1102, a Network FunctionsVirtualization Infrastructure (NFVI) 1104, a Virtualized NetworkFunction Manager (VNFM) 1106, VNFs 1108, an Element Manager (EM) 1110, aNetwork Functions Virtualization Orchestrator (NFVO) 1112, and a NetworkManager (NM) 1114.

The VIM 1102 manages the resources of the NFVI 1104. The NFVI 1104 caninclude physical or virtual resources and applications (includinghypervisors) used to execute the system 1100. The VIM 1102 may managethe life cycle of virtual resources with the NFVI 1104 (e.g., creation,maintenance, and tear down of Virtual Machines (VMs) associated with oneor more physical resources), track VM instances, track performance,fault and security of VM instances and associated physical resources,and expose VM instances and associated physical resources to othermanagement systems.

The VNFM 1106 may manage the VNFs 1108. The VNFs 1108 may be used toexecute Evolved Packet Core (EPC) components/functions. The VNFM 1106may manage the life cycle of the VNFs 1108 and track performance, faultand security of the virtual aspects of VNFs 1108. The EM 1110 may trackthe performance, fault and security of the functional aspects of VNFs1108. The tracking data from the VNFM 1106 and the EM 1110 may comprise,for example, PM data used by the VIM 1102 or the NFVI 1104. Both theVNFM 1106 and the EM 1910 can scale up/down the quantity of VNFs of thesystem 1100.

The NFVO 1112 may coordinate, authorize, release and engage resources ofthe NFVI 1104 in order to provide the requested service (e.g., toexecute an EPC function, component, or slice). The NM 1114 provides apackage of end-user functions with the responsibility for the managementof a network, which can include network elements with VNFs,non-virtualized network functions, or both (management of the VNFs mayoccur via the EM 1110).

FIG. 12 is a block diagram illustrating components, according to someexample embodiments, able to read instructions from a machine-readableor computer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein. Specifically, FIG. 12 shows a diagrammaticrepresentation of hardware resources 1200 including one or moreprocessors (or processor cores) 1210, one or more memory/storage devices1220, and one or more communication resources 1230, each of which may becommunicatively coupled via a bus 1240. For embodiments where nodevirtualization (e.g., NFV) is utilized, a hypervisor 1202 may beexecuted to provide an execution environment for one or more networkslices/sub-slices to utilize the hardware resources 1200.

The processors 1210 can include, for example, a processor 1212 and aprocessor 1214. The processor(s) 1210 may be, for example, a centralprocessing unit (CPU), a reduced instruction set computing (RISC)processor, a complex instruction set computing (CISC) processor, agraphics processing unit (GPU), a DSP such as a baseband processor, anASIC, an FPGA, a radio-frequency integrated circuit (RFIC), anotherprocessor (including those discussed herein), or any suitablecombination thereof.

The memory/storage devices 1220 can include main memory, disk storage,or any suitable combination thereof. The memory/storage devices 1220 caninclude, but are not limited to, any type of volatile or nonvolatilememory such as dynamic random access memory (DRAM), static random accessmemory (SRAM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), Flashmemory, solid-state storage, etc.

The communication resources 1230 can include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 1204 or one or more databases 1206 via anetwork 1208. For example, the communication resources 1230 can includewired communication components (e.g., for coupling via USB), cellularcommunication components, NFC components, Bluetooth® (or Bluetooth® LowEnergy) components, Wi-Fi® components, and other communicationcomponents.

Instructions 1250 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 1210 to perform any one or more of the methodologiesdiscussed herein. The instructions 1250 may reside, completely orpartially, within at least one of the processors 1210 (e.g., within theprocessor's cache memory), the memory/storage devices 1220, or anysuitable combination thereof. Furthermore, any portion of theinstructions 1250 may be transferred to the hardware resources 1200 fromany combination of the peripheral devices 1204 or the databases 1206.Accordingly, the memory of processors 1210, the memory/storage devices1220, the peripheral devices 1204, and the databases 1206 are examplesof computer-readable and machine-readable media.

FIG. 13 illustrates a process 1300 performed by a first access nodeaccording to for implementing a cross-link interference (CLI)information exchange procedure in a wireless communication systemaccording to embodiments of the disclosure. In step 1302, a CLI requestsignal is received from a second access node. In step 1304, a CLIresponse signal is generated, the CLI response signal includingtime-division duplex (TDD) configuration information. In step 1306, theCLI response signal is transmitted to the second access node. The TDDconfiguration information can be implemented for wireless communicationat the first access node and/or second access node.

FIG. 14 illustrates a process 1400 performed by a first access nodeaccording for implementing a cross-link interference (CLI) informationexchange procedure in a wireless communication system according toembodiments of the disclosure. In step 1402, a CLI request signal isgenerated at the first access node and transmitted to a second accessnode. In step 1404, a CLI response signal is receive from the secondaccess node, the CLI response signal including time-division duplex(TDD) configuration information. The TDD configuration information canbe implemented for wireless communication at the first access nodeand/or second access node.

The processes and functions illustrated in FIGS. 13-14 can be performedby one or more of application circuitry 605 or 705, baseband circuitry610 or 710, or processors 1214.

Exemplary Embodiments

The exemplary embodiments set forth herein are illustrative and notexhaustive. These exemplary embodiments are not meant to be limiting.

Some embodiments can includes an apparatus. The apparatus can beconfigured to:

transmit a cross-link information (CLI) request message to anext-generation NodeB (gNB); and

receive a CLI response message from the gNB, the CLI response messagecomprising time-division duplex (TDD) configuration information.

Some embodiments can includes an apparatus. The apparatus can beconfigured to:

receive a cross-link information (CLI) request message from anext-generation NodeB (gNB); and

transmit a CLI response message to the gNB, the CLI response messagecomprising time-division duplex (TDD) configuration information.

Some embodiments can includes an apparatus. The apparatus can beconfigured to:

generate a cross-link information (CLI) request signal;

transmit the CLI request signal to a next-generation NodeB (gNB); and

receive a CLI response signal from the gNB, the CLI response signalcomprising time-division duplex (TDD) configuration information.

Some embodiments can includes an apparatus. The apparatus can beconfigured to:

receive a cross-link information (CLI) request signal from anext-generation NodeB (gNB);

generate a CLI response signal, the CLI response signal comprisingtime-division duplex (TDD) configuration information; and

transmit the CLI response signal to the gNB.

In these above embodiments, the apparatus can be a next-generation NodeB(gNB) or a portion thereof.

Some embodiments can include a method. The method includes:

transmitting or causing to transmit a cross-link information (CLI)request message to a next-generation NodeB (gNB); and

receiving or causing to receive a CLI response message from the gNB, theCLI response message comprising time-division duplex (TDD) configurationinformation.

Some embodiments can include a method. The method includes:

receiving or causing to receive a cross-link information (CLI) requestmessage from a next-generation NodeB (gNB); and

transmitting or causing to transmit a CLI response message to the gNB,the CLI response message comprising time-division duplex (TDD)configuration information.

In these above embodiments, the method can be performed by anext-generation nodeB (gNB) or a portion thereof.

Some embodiments can include a procedure “CLI INFORMATION EXCHANGE” forexchange of information for coordination of configuration cross-linkinterference reference signals. The procedure can include:

transmitting or receiving a CLI INFORMATION REQUEST message; and

transmitting or receiving a CLI INFORMATION RESPONSE message.

In these embodiments, the CLI INFORMATION RESPONSE message can includeone or more of:

1. List of TDD Configurations, such as Cell ID and Common TDDConfiguration. In these embodiments, the Common TDD Configuration canindicate the cell-specific TDD DL/UL Configuration configured for cellcorresponding to Cell ID.

2. List of Dedicated TDD Configurations, such as Dedicated TDDConfiguration and UE ID. In these embodiments, the Dedicated TDDConfiguration can indicate a UE-specific TDD DL/UL Configuration. Inthese embodiments, the UE ID can indicate the identity of thecorresponding UE configured with Dedicated TDD Configuration.

3. List of UE CLI RS Transmission Configurations, such as UE CLI RSTransmission Configuration and UE ID. In these embodiments, the UE IDcan indicate the identity of the corresponding UE configured with UE CLIRS Transmission Configuration.

In these embodiments, the UE CLI RS Transmission Configuration can bethe information element SRS-Config (defined in TS36.331).

In these embodiments, the UE CLI RS Transmission Configuration can bethe information element CLI-RS-TxResourceConfig (described in IDFAB8766).

In these embodiments, the CLI INFORMATION REQUEST message and CLIINFORMATION RESPONSE message can be communicated over Xn interface.

In these embodiments, the CLI INFORMATION REQUEST message and CLIINFORMATION RESPONSE message can be communicated over F1 interface.

Some embodiments can include an apparatus comprising means to performone or more elements of a method described in or related to any of theembodiments described above, or any other method or process describedherein.

Some embodiments can include one or more non-transitorycomputer-readable media comprising instructions to cause an electronicdevice, upon execution of the instructions by one or more processors ofthe electronic device, to perform one or more elements of a methoddescribed in or related to any of the embodiments described above, orany other method or process described herein.

Some embodiments can include an apparatus comprising logic, modules, orcircuitry to perform one or more elements of a method described in orrelated to any of the embodiments described above, or any other methodor process described herein.

Some embodiments can include a method, technique, or process asdescribed in or related to any of the embodiments described above, orportions or parts thereof.

Some embodiments can include an apparatus comprising: one or moreprocessors and one or more computer-readable media comprisinginstructions that, when executed by the one or more processors, causethe one or more processors to perform the method, techniques, or processas described in or related to any of the embodiments described above, orportions thereof.

Some embodiments can include a signal as described in or related to anyof the embodiments described above, or portions or parts thereof.

Some embodiments can include a signal in a wireless network as shown anddescribed herein.

Some embodiments can include a method of communicating in a wirelessnetwork as shown and described herein.

Some embodiments can include a system for providing wirelesscommunication as shown and described herein.

Some embodiments can include a device for providing wirelesscommunication as shown and described herein.

Some embodiments can include an apparatus comprising means forperforming one or more of the methods described above in connection withthe embodiments described above.

Some embodiments can include an apparatus comprising circuitryconfigured to perform one or more of the methods described above inconnection with the embodiments described above.

Some embodiments can include an apparatus according to any of any one ofthe embodiments described above, wherein the apparatus or any portionthereof is implemented in or by a user equipment (UE).

Some embodiments can include a method according to any of any one of theembodiments described above, wherein the method or any portion thereofis implemented in or by a user equipment (UE).

Some embodiments can include an apparatus according to any of any one ofthe embodiments described above, wherein the apparatus or any portionthereof is implemented in or by a base station (BS).

Some embodiments can include a method according to any of any one of theembodiments described above, wherein the method or any portion thereofis implemented in or by a base station (BS).

Any of the above-described embodiments may be combined with any otherembodiments (or combination of embodiments), unless explicitly statedotherwise. The foregoing description of one or more implementationsprovides illustration and description, but is not intended to beexhaustive or to limit the scope of embodiments to the precise formdisclosed. Modifications and variations are possible in light of theabove teachings or may be acquired from practice of various embodiments.

Abbreviations

For the purposes of this disclosure, the following abbreviations mayapply to the examples and embodiments discussed herein, but are notmeant to be limiting.

-   -   3GPP Third Generation Partnership Project    -   4G Fourth Generation    -   5G Fifth Generation    -   5GC 5G Core network    -   ACK Acknowledgement    -   AF Application Function    -   AM Acknowledged Mode    -   AMBR Aggregate Maximum Bit Rate    -   AMF Access and Mobility Management Function    -   AN Access Network    -   ANR Automatic Neighbour Relation    -   AP Application Protocol, Antenna Port, Access Point    -   API Application Programming Interface    -   APN Access Point Name    -   ARP Allocation and Retention Priority    -   ARQ Automatic Repeat Request    -   AS Access Stratum    -   ASN.1 Abstract Syntax Notation One    -   AUSF Authentication Server Function    -   AWGN Additive White Gaussian Noise    -   BCH Broadcast Channel    -   BER Bit Error Ratio    -   BFD Beam Failure Detection    -   BLER Block Error Rate    -   BPSK Binary Phase Shift Keying    -   BRAS Broadband Remote Access Server    -   BSS Business Support System    -   BS Base Station    -   BSR Buffer Status Report    -   BW Bandwidth    -   BWP Bandwidth Part    -   C-RNTI Cell Radio Network Temporary Identity    -   CA Carrier Aggregation, Certification Authority    -   CAPEX CAPital EXpenditure    -   CBRA Contention Based Random Access    -   CC Component Carrier, Country Code, Cryptographic Checksum    -   CCA Clear Channel Assessment    -   CCE Control Channel Element    -   CCCH Common Control Channel    -   CE Coverage Enhancement    -   CDM Content Delivery Network    -   CDMA Code-Division Multiple Access    -   CFRA Contention Free Random Access    -   CG Cell Group    -   CI Cell Identity    -   CID Cell-ID (e.g., positioning method)    -   CIM Common Information Model    -   CIR Carrier to Interference Ratio    -   CK Cipher Key    -   CM Connection Management, Conditional Mandatory    -   CMAS Commercial Mobile Alert Service    -   CMD Command    -   CMS Cloud Management System    -   CO Conditional Optional    -   CoMP Coordinated Multi-Point    -   CORESET Control Resource Set    -   COTS Commercial Off-The-Shelf    -   CP Control Plane, Cyclic Prefix, Connection Point    -   CPD Connection Point Descriptor    -   CPE Customer Premise Equipment    -   CPICH Common Pilot Channel    -   CQI Channel Quality Indicator    -   CPU CSI processing unit, Central Processing Unit    -   C/R Command/Response field bit    -   CRAN Cloud Radio Access Network, Cloud RAN    -   CRB Common Resource Block    -   CRC Cyclic Redundancy Check    -   CRI Channel-State Information Resource Indicator, CSI-RS        Resource Indicator    -   C-RNTI Cell RNTI    -   CS Circuit Switched    -   CSAR Cloud Service Archive    -   CSI Channel-State Information    -   CSI-IM CSI Interference Measurement    -   CSI-RS CSI Reference Signal    -   CSI-RSRP CSI reference signal received power    -   CSI-RSRQ CSI reference signal received quality    -   CSI-SINR CSI signal-to-noise and interference ratio    -   CSMA Carrier Sense Multiple Access    -   CSMA/CA CSMA with collision avoidance    -   CSS Common Search Space, Cell-specific Search Space    -   CTS Clear-to-Send    -   CW Codeword    -   CWS Contention Window Size    -   D2D Device-to-Device    -   DC Dual Connectivity, Direct Current    -   DCI Downlink Control Information    -   DF Deployment Flavour    -   DL Downlink    -   DMTF Distributed Management Task Force    -   DPDK Data Plane Development Kit    -   DM-RS, DMRS Demodulation Reference Signal    -   DN Data network    -   DRB Data Radio Bearer    -   DRS Discovery Reference Signal    -   DRX Discontinuous Reception    -   DSL Domain Specific Language. Digital Subscriber Line    -   DSLAM DSL Access Multiplexer    -   DwPTS Downlink Pilot Time Slot    -   E-LAN Ethernet Local Area Network    -   E2E End-to-End    -   ECCA extended clear channel assessment, extended CCA    -   ECCE Enhanced Control Channel Element, Enhanced CCE    -   ED Energy Detection    -   EDGE Enhanced Datarates for GSM Evolution (GSM Evolution)    -   EGMF Exposure Governance Management Function    -   EGPRS Enhanced GPRS    -   EIR Equipment Identity Register    -   eLAA enhanced Licensed Assisted Access, enhanced LAA    -   EM Element Manager    -   eMBB Enhanced Mobile Broadband    -   EMS Element Management System    -   eNB evolved NodeB, E-UTRAN Node B    -   EN-DC E-UTRA-NR Dual Connectivity    -   EPC Evolved Packet Core    -   EPDCCH enhanced PDCCH, enhanced Physical Downlink Control Cannel    -   EPRE Energy per resource element    -   EPS Evolved Packet System    -   EREG enhanced REG, enhanced resource element groups    -   ETSI European Telecommunications Standards Institute    -   ETWS Earthquake and Tsunami Warning System    -   eUICC embedded UICC, embedded Universal Integrated Circuit Card    -   E-UTRA Evolved UTRA    -   E-UTRAN Evolved UTRAN    -   EV2X Enhanced V2X    -   F1AP F1 Application Protocol    -   F1-C F1 Control plane interface    -   F1-U F1 User plane interface    -   FACCH Fast Associated Control CHannel    -   FACCH/F Fast Associated Control Channel/Full rate    -   FACCH/H Fast Associated Control Channel/Half rate    -   FACH Forward Access Channel    -   FAUSCH Fast Uplink Signalling Channel    -   FB Functional Block    -   FBI Feedback Information    -   FCC Federal Communications Commission    -   FCCH Frequency Correction CHannel    -   FDD Frequency Division Duplex    -   FDM Frequency Division Multiplex    -   FDMA Frequency Division Multiple Access    -   FE Front End    -   FEC Forward Error Correction    -   FFS For Further Study    -   FFT Fast Fourier Transformation    -   feLAA further enhanced Licensed Assisted Access, further        enhanced LAA    -   FN Frame Number    -   FPGA Field-Programmable Gate Array    -   FR Frequency Range    -   G-RNTI GERAN Radio Network Temporary Identity    -   GERAN GSM EDGE RAN, GSM EDGE Radio Access Network    -   GGSN Gateway GPRS Support Node    -   GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Engl.:        Global Navigation Satellite System)    -   gNB Next Generation NodeB    -   gNB-CU gNB-centralized unit, Next Generation NodeB centralized        unit    -   gNB-DU gNB-distributed unit, Next Generation NodeB distributed        unit    -   GNSS Global Navigation Satellite System    -   GPRS General Packet Radio Service    -   GSM Global System for Mobile Communications, Groupe Special        Mobile    -   GTP GPRS Tunneling Protocol    -   GTP-U GPRS Tunnelling Protocol for User Plane    -   GTS Go To Sleep Signal (related to WUS)    -   GUMMEI Globally Unique MME Identifier    -   GUTI Globally Unique Temporary UE Identity    -   HARQ Hybrid ARQ, Hybrid Automatic Repeat Request    -   HANDO, HO Handover    -   HFN HyperFrame Number    -   HHO Hard Handover    -   HLR Home Location Register    -   HN Home Network    -   HO Handover    -   HPLMN Home Public Land Mobile Network    -   HSDPA High Speed Downlink Packet Access    -   HSN Hopping Sequence Number    -   HSPA High Speed Packet Access    -   HSS Home Subscriber Server    -   HSUPA High Speed Uplink Packet Access    -   HTTP Hyper Text Transfer Protocol    -   HTTPS Hyper Text Transfer Protocol Secure (https is http/1.1        over SSL, i.e. port 443)    -   I-Block Information Block    -   ICCID Integrated Circuit Card Identification    -   ICIC Inter-Cell Interference Coordination    -   ID Identity, identifier    -   IDFT Inverse Discrete Fourier Transform    -   IE Information element    -   IBE In-Band Emission    -   IEEE Institute of Electrical and Electronics Engineers    -   IEI Information Element Identifier    -   IEIDL Information Element Identifier Data Length    -   IETF Internet Engineering Task Force    -   IF Infrastructure    -   IM Interference Measurement, Intermodulation, IP Multimedia    -   IMC IMS Credentials    -   IMEI International Mobile Equipment Identity    -   IMGI International mobile group identity    -   IMPI IP Multimedia Private Identity    -   IMPU IP Multimedia PUblic identity    -   IMS IP Multimedia Subsystem    -   IMSI International Mobile Subscriber Identity    -   IoT Internet of Things    -   IP Internet Protocol    -   Ipsec IP Security, Internet Protocol Security    -   IP-CAN IP-Connectivity Access Network    -   IP-M IP Multicast    -   IPv4 Internet Protocol Version 4    -   IPv6 Internet Protocol Version 6    -   IR Infrared    -   IS In Sync    -   IRP Integration Reference Point    -   ISDN Integrated Services Digital Network    -   ISIM IM Services Identity Module    -   ISO International Organisation for Standardisation    -   ISP Internet Service Provider    -   IWF Interworking-Function    -   I-WLAN Interworking WLAN    -   K Constraint length of the convolutional code, USIM Individual        key    -   kB Kilobyte (500 bytes)    -   kbps kilo-bits per second    -   Kc Ciphering key    -   Ki Individual subscriber authentication key    -   KPI Key Performance Indicator    -   KQI Key Quality Indicator    -   KSI Key Set Identifier    -   ksps kilo-symbols per second    -   KVM Kernel Virtual Machine    -   L1 Layer 1 (physical layer)    -   L1-RSRP Layer 1 reference signal received power    -   L2 Layer 2 (data link layer)    -   L3 Layer 3 (network layer)    -   LAA Licensed Assisted Access    -   LAN Local Area Network    -   LBT Listen Before Talk    -   LCM LifeCycle Management    -   LCR Low Chip Rate    -   LCS Location Services    -   LCID Logical Channel ID    -   LI Layer Indicator    -   LLC Logical Link Control, Low Layer Compatibility    -   LPLMN Local PLMN    -   LPP LTE Positioning Protocol    -   LSB Least Significant Bit    -   LTE Long Term Evolution    -   LWA LTE-WLAN aggregation    -   LWIP LTE/WLAN Radio Level Integration with IPsec Tunnel    -   LTE Long Term Evolution    -   M2M Machine-to-Machine    -   MAC Medium Access Control (protocol layering context)    -   MAC Message authentication code (security/encryption context)    -   MAC-A MAC used for authentication and key agreement (TSG T WG3        context)    -   MAC-I MAC used for data integrity of signalling messages (TSG T        WG3 context)    -   MANO Management and Orchestration    -   MBMS Multimedia Broadcast and Multicast Service    -   MBSFN Multimedia Broadcast multicast service Single Frequency        Network    -   MCC Mobile Country Code    -   MCG Master Cell Group    -   MCOT Maximum Channel Occupancy Time    -   MCS Modulation and coding scheme    -   MDAF Management Data Analytics Function    -   MDAS Management Data Analytics Service    -   MDT Minimization of Drive Tests    -   ME Mobile Equipment    -   MeNB master eNB    -   MER Message Error Ratio    -   MGL Measurement Gap Length    -   MGRP Measurement Gap Repetition Period    -   MIB Master Information Block, Management Information Base    -   MIMO Multiple Input Multiple Output    -   MLC Mobile Location Centre    -   MM Mobility Management    -   MME Mobility Management Entity    -   MN Master Node    -   MO Measurement Object, Mobile Originated    -   MPBCH MTC Physical Broadcast CHannel    -   MPDCCH MTC Physical Downlink Control CHannel    -   MPDSCH MTC Physical Downlink Shared CHannel    -   MPRACH MTC Physical Random Access CHannel    -   MPUSCH MTC Physical Uplink Shared Channel    -   MPLS MultiProtocol Label Switching    -   MS Mobile Station    -   MSB Most Significant Bit    -   MSC Mobile Switching Centre    -   MSI Minimum System Information, MCH Scheduling Information    -   MSID Mobile Station Identifier    -   MSIN Mobile Station Identification Number    -   MSISDN Mobile Subscriber ISDN Number    -   MT Mobile Terminated, Mobile Termination    -   MTC Machine-Type Communications    -   mMTC massive MTC, massive Machine-Type Communications    -   MU-MIMO Multi User MIMO    -   MWUS MTC wake-up signal, MTC WUS    -   NACK Negative Acknowledgement    -   NAI Network Access Identifier    -   NAS Non-Access Stratum, Non-Access Stratum layer    -   NCT Network Connectivity Topology    -   NEC Network Capability Exposure    -   NE-DC NR-E-UTRA Dual Connectivity    -   NEF Network Exposure Function    -   NF Network Function    -   NFP Network Forwarding Path    -   NFPD Network Forwarding Path Descriptor    -   NFV Network Functions Virtualization    -   NFVI NFV Infrastructure    -   NFVO NFV Orchestrator    -   NG Next Generation, Next Gen    -   NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity    -   NM Network Manager    -   NMS Network Management System    -   N-PoP Network Point of Presence    -   NMIB, N-MIB Narrowband MIB    -   NPBCH Narrowband Physical Broadcast CHannel    -   NPDCCH Narrowband Physical Downlink Control CHannel    -   NPDSCH Narrowband Physical Downlink Shared CHannel    -   NPRACH Narrowband Physical Random Access CHannel    -   NPUSCH Narrowband Physical Uplink Shared CHannel    -   NPSS Narrowband Primary Synchronization Signal    -   NSSS Narrowband Secondary Synchronization Signal    -   NR New Radio, Neighbour Relation    -   NRF NF Repository Function    -   NRS Narrowband Reference Signal    -   NS Network Service    -   NSA Non-Standalone operation mode    -   NSD Network Service Descriptor    -   NSR Network Service Record    -   NSSAI ‘Network Slice Selection Assistance Information    -   S-NNSAI Single-NSSAI    -   NSSF Network Slice Selection Function    -   NW Network    -   NWUS Narrowband wake-up signal, Narrowband WUS    -   NZP Non-Zero Power    -   O&M Operation and Maintenance    -   ODU2 Optical channel Data Unit—type 2    -   OFDM Orthogonal Frequency Division Multiplexing    -   OFDMA Orthogonal Frequency Division Multiple Access    -   OOB Out-of-band    -   OOS Out of Sync    -   OPEX OPerating EXpense    -   OSI Other System Information    -   OSS Operations Support System    -   OTA over-the-air    -   PAPR Peak-to-Average Power Ratio    -   PAR Peak to Average Ratio    -   PBCH Physical Broadcast Channel    -   PC Power Control, Personal Computer    -   PCC Primary Component Carrier, Primary CC    -   PCell Primary Cell    -   PCI Physical Cell ID, Physical Cell Identity    -   PCEF Policy and Charging Enforcement Function    -   PCF Policy Control Function    -   PCRF Policy Control and Charging Rules Function    -   PDCP Packet Data Convergence Protocol, Packet Data Convergence        Protocol layer    -   PDCCH Physical Downlink Control Channel    -   PDCP Packet Data Convergence Protocol    -   PDN Packet Data Network, Public Data Network    -   PDSCH Physical Downlink Shared Channel    -   PDU Protocol Data Unit    -   PEI Permanent Equipment Identifiers    -   PFD Packet Flow Description    -   P-GW PDN Gateway    -   PHICH Physical hybrid-ARQ indicator channel    -   PHY Physical layer    -   PLMN Public Land Mobile Network    -   PIN Personal Identification Number    -   PM Performance Measurement    -   PMI Precoding Matrix Indicator    -   PNF Physical Network Function    -   PNFD Physical Network Function Descriptor    -   PNFR Physical Network Function Record    -   POC PTT over Cellular    -   PP, PTP Point-to-Point    -   PPP Point-to-Point Protocol    -   PRACH Physical RACH    -   PRB Physical resource block    -   PRG Physical resource block group    -   ProSe Proximity Services, Proximity-Based Service    -   PRS Positioning Reference Signal    -   PRR Packet Reception Radio    -   PS Packet Services    -   PSBCH Physical Sidelink Broadcast Channel    -   PSDCH Physical Sidelink Downlink Channel    -   PSCCH Physical Sidelink Control Channel    -   PSSCH Physical Sidelink Shared Channel    -   PSCell Primary SCell    -   PSS Primary Synchronization Signal    -   PSTN Public Switched Telephone Network    -   PT-RS Phase-tracking reference signal    -   PTT Push-to-Talk    -   PUCCH Physical Uplink Control Channel    -   PUSCH Physical Uplink Shared Channel    -   QAM Quadrature Amplitude Modulation    -   QCI QoS class of identifier    -   QCL Quasi co-location    -   QFI QoS Flow ID, QoS Flow Identifier    -   QoS Quality of Service    -   QPSK Quadrature (Quaternary) Phase Shift Keying    -   QZSS Quasi-Zenith Satellite System    -   RA-RNTI Random Access RNTI    -   RAB Radio Access Bearer, Random Access Burst    -   RACH Random Access Channel    -   RADIUS Remote Authentication Dial In User Service    -   RAN Radio Access Network    -   RAND RANDom number (used for authentication)    -   RAR Random Access Response    -   RAT Radio Access Technology    -   RAU Routing Area Update    -   RB Resource block, Radio Bearer    -   RBG Resource block group    -   REG Resource Element Group    -   Rel Release    -   REQ REQuest    -   RF Radio Frequency    -   RI Rank Indicator    -   RIV Resource indicator value    -   RL Radio Link    -   RLC Radio Link Control, Radio Link Control layer    -   RLC AM RLC Acknowledged Mode    -   RLC UM RLC Unacknowledged Mode    -   RLF Radio Link Failure    -   RLM Radio Link Monitoring    -   RLM-RS Reference Signal for RLM    -   RM Registration Management    -   RMC Reference Measurement Channel    -   RMSI Remaining MSI, Remaining Minimum System Information    -   RN Relay Node    -   RNC Radio Network Controller    -   RNL Radio Network Layer    -   RNTI Radio Network Temporary Identifier    -   ROHC RObust Header Compression    -   RRC Radio Resource Control, Radio Resource Control layer    -   RRM Radio Resource Management    -   RS Reference Signal    -   RSRP Reference Signal Received Power    -   RSRQ Reference Signal Received Quality    -   RSSI Received Signal Strength Indicator    -   RSU Road Side Unit    -   RSTD Reference Signal Time difference    -   RTP Real Time Protocol    -   RTS Ready-To-Send    -   RTT Round Trip Time    -   Rx Reception, Receiving, Receiver    -   S1AP S1 Application Protocol    -   S1-MME S1 for the control plane    -   S1-U S1 for the user plane    -   S-GW Serving Gateway    -   S-RNTI SRNC Radio Network Temporary Identity    -   S-TMSI SAE Temporary Mobile Station Identifier    -   SA Standalone operation mode    -   SAE System Architecture Evolution    -   SAP Service Access Point    -   SAPD Service Access Point Descriptor    -   SAPI Service Access Point Identifier    -   SCC Secondary Component Carrier, Secondary CC    -   SCell Secondary Cell    -   SC-FDMA Single Carrier Frequency Division Multiple Access    -   SCG Secondary Cell Group    -   SCM Security Context Management    -   SCS Subcarrier Spacing    -   SCTP Stream Control Transmission Protocol    -   SDAP Service Data Adaptation Protocol, Service Data Adaptation        Protocol layer    -   SDL Supplementary Downlink    -   SDNF Structured Data Storage Network Function    -   SDP Service Discovery Protocol (Bluetooth related)    -   SDSF Structured Data Storage Function    -   SDU Service Data Unit    -   SEAF Security Anchor Function    -   SeNB secondary eNB    -   SEPP Security Edge Protection Proxy    -   SFI Slot format indication    -   SFTD Space-Frequency Time Diversity, SFN and frame timing        difference    -   SFN System Frame Number    -   SgNB Secondary gNB    -   SGSN Serving GPRS Support Node    -   S-GW Serving Gateway    -   SI System Information    -   SI-RNTI System Information RNTI    -   SIB System Information Block    -   SIM Subscriber Identity Module    -   SIP Session Initiated Protocol    -   SiP System in Package    -   SL Sidelink    -   SLA Service Level Agreement    -   SM Session Management    -   SMF Session Management Function    -   SMS Short Message Service    -   SMSF SMS Function    -   SMTC SSB-based Measurement Timing Configuration    -   SN Secondary Node, Sequence Number    -   SoC System on Chip    -   SON Self-Organizing Network    -   SpCell Special Cell    -   SP-CSI-RNTI Semi-Persistent CSI RNTI    -   SPS Semi-Persistent Scheduling    -   SQN Sequence number    -   SR Scheduling Request    -   SRB Signalling Radio Bearer    -   SRS Sounding Reference Signal    -   SS Synchronization Signal    -   SSB Synchronization Signal Block, SS/PBCH Block    -   SSBRI SS/PBCH Block Resource Indicator, Synchronization Signal        Block Resource Indicator    -   SSC Session and Service Continuity    -   SS-RSRP Synchronization Signal based Reference Signal Received        Power    -   SS-RSRQ Synchronization Signal based Reference Signal Received        Quality    -   SS-SINR Synchronization Signal based Signal to Noise and        Interference Ratio    -   SSS Secondary Synchronization Signal    -   SSSG Search Space Set Group    -   SSSIF Search Space Set Indicator    -   SST Slice/Service Types    -   SU-MIMO Single User MIMO    -   SUL Supplementary Uplink    -   TA Timing Advance, Tracking Area    -   TAC Tracking Area Code    -   TAG Timing Advance Group    -   TAU Tracking Area Update    -   TB Transport Block    -   TBS Transport Block Size    -   TBD To Be Defined    -   TCI Transmission Configuration Indicator    -   TCP Transmission Communication Protocol    -   TDD Time Division Duplex    -   TDM Time Division Multiplexing    -   TDMA Time Division Multiple Access    -   TE Terminal Equipment    -   TEID Tunnel End Point Identifier    -   TFT Traffic Flow Template    -   TMSI Temporary Mobile Subscriber Identity    -   TNL Transport Network Layer    -   TPC Transmit Power Control    -   TPMI Transmitted Precoding Matrix Indicator    -   TR Technical Report    -   TRP, TRxP Transmission Reception Point    -   TRS Tracking Reference Signal    -   TRx Transceiver    -   TS Technical Specifications, Technical Standard    -   TTI Transmission Time Interval    -   Tx Transmission, Transmitting, Transmitter    -   U-RNTI UTRAN Radio Network Temporary Identity    -   UART Universal Asynchronous Receiver and Transmitter    -   UCI Uplink Control Information    -   UE User Equipment    -   UDM Unified Data Management    -   UDP User Datagram Protocol    -   UDSF Unstructured Data Storage Network Function    -   UICC Universal Integrated Circuit Card    -   UL Uplink    -   UM Unacknowledged Mode    -   UML Unified Modelling Language    -   UMTS Universal Mobile Telecommunications System    -   UP User Plane    -   UPF User Plane Function    -   URI Uniform Resource Identifier    -   URL Uniform Resource Locator    -   URLLC Ultra-Reliable and Low Latency    -   USB Universal Serial Bus    -   USIM Universal Subscriber Identity Module    -   USS UE-specific search space    -   UTRA UMTS Terrestrial Radio Access    -   UTRAN Universal Terrestrial Radio Access Network    -   UwPTS Uplink Pilot Time Slot    -   V2I Vehicle-to-Infrastruction    -   V2P Vehicle-to-Pedestrian    -   V2V Vehicle-to-Vehicle    -   V2X Vehicle-to-everything    -   VIM Virtualized Infrastructure Manager    -   VL Virtual Link,    -   VLAN Virtual LAN, Virtual Local Area Network    -   VM Virtual Machine    -   VNF Virtualized Network Function    -   VNFFG VNF Forwarding Graph    -   VNFFGD VNF Forwarding Graph Descriptor    -   VNFM VNF Manager    -   VoIP Voice-over-IP, Voice-over-Internet Protocol    -   VPLMN Visited Public Land Mobile Network    -   VPN Virtual Private Network    -   VRB Virtual Resource Block    -   WiMAX Worldwide Interoperability for Microwave Access    -   WLAN Wireless Local Area Network    -   WMAN Wireless Metropolitan Area Network    -   WPAN Wireless Personal Area Network    -   X2-C X2-Control plane    -   X2-U X2-User plane    -   XML eXtensible Markup Language    -   2ES EXpected user RESponse    -   XOR eXclusive OR    -   ZC Zadoff-Chu    -   ZP Zero Power

Exemplary Terminology

For the purposes of the present document, the following terms anddefinitions are applicable to the examples and embodiments discussedherein, but are not meant to be limiting.

The term “circuitry” as used herein refers to, is part of, or includeshardware components such as an electronic circuit, a logic circuit, aprocessor (shared, dedicated, or group) and/or memory (shared,dedicated, or group), an Application Specific Integrated Circuit (ASIC),a field-programmable device (FPD) (e.g., a field-programmable gate array(FPGA), a programmable logic device (PLD), a complex PLD (CPLD), ahigh-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC),digital signal processors (DSPs), etc., that are configured to providethe described functionality. In some embodiments, the circuitry mayexecute one or more software or firmware programs to provide at leastsome of the described functionality. The term “circuitry” may also referto a combination of one or more hardware elements (or a combination ofcircuits used in an electrical or electronic system) with the programcode used to carry out the functionality of that program code. In theseembodiments, the combination of hardware elements and program code maybe referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, orincludes circuitry capable of sequentially and automatically carryingout a sequence of arithmetic or logical operations, or recording,storing, and/or transferring digital data. The term “processorcircuitry” may refer to one or more application processors, one or morebaseband processors, a physical central processing unit (CPU), asingle-core processor, a dual-core processor, a triple-core processor, aquad-core processor, and/or any other device capable of executing orotherwise operating computer-executable instructions, such as programcode, software modules, and/or functional processes. The terms“application circuitry” and/or “baseband circuitry” may be consideredsynonymous to, and may be referred to as, “processor circuitry.”

The term “interface circuitry” as used herein refers to, is part of, orincludes circuitry that enables the exchange of information between twoor more components or devices. The term “interface circuitry” may referto one or more hardware interfaces, for example, buses, I/O interfaces,peripheral component interfaces, network interface cards, and/or thelike.

The term “user equipment” or “UE” as used herein refers to a device withradio communication capabilities and may describe a remote user ofnetwork resources in a communications network. The term “user equipment”or “UE” may be considered synonymous to, and may be referred to as,client, mobile, mobile device, mobile terminal, user terminal, mobileunit, mobile station, mobile user, subscriber, user, remote station,access agent, user agent, receiver, radio equipment, reconfigurableradio equipment, reconfigurable mobile device, etc. Furthermore, theterm “user equipment” or “UE” can include any type of wireless/wireddevice or any computing device including a wireless communicationsinterface.

The term “network element” as used herein refers to physical orvirtualized equipment and/or infrastructure used to provide wired orwireless communication network services. The term “network element” maybe considered synonymous to and/or referred to as a networked computer,networking hardware, network equipment, network node, router, switch,hub, bridge, radio network controller, RAN device, RAN node, gateway,server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any typeinterconnected electronic devices, computer devices, or componentsthereof. Additionally, the term “computer system” and/or “system” mayrefer to various components of a computer that are communicativelycoupled with one another. Furthermore, the term “computer system” and/or“system” may refer to multiple computer devices and/or multiplecomputing systems that are communicatively coupled with one another andconfigured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used hereinrefers to a computer device or computer system with program code (e.g.,software or firmware) that is specifically designed to provide aspecific computing resource. A “virtual appliance” is a virtual machineimage to be implemented by a hypervisor-equipped device that virtualizesor emulates a computer appliance or otherwise is dedicated to provide aspecific computing resource.

The term “resource” as used herein refers to a physical or virtualdevice, a physical or virtual component within a computing environment,and/or a physical or virtual component within a particular device, suchas computer devices, mechanical devices, memory space, processor/CPUtime, processor/CPU usage, processor and accelerator loads, hardwaretime or usage, electrical power, input/output operations, ports ornetwork sockets, channel/link allocation, throughput, memory usage,storage, network, database and applications, workload units, and/or thelike. A “hardware resource” may refer to compute, storage, and/ornetwork resources provided by physical hardware element(s). A“virtualized resource” may refer to compute, storage, and/or networkresources provided by virtualization infrastructure to an application,device, system, etc. The term “network resource” or “communicationresource” may refer to resources that are accessible by computerdevices/systems via a communications network. The term “systemresources” may refer to any kind of shared entities to provide services,and can include computing and/or network resources. System resources maybe considered as a set of coherent functions, network data objects orservices, accessible through a server where such system resources resideon a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium,either tangible or intangible, which is used to communicate data or adata stream. The term “channel” may be synonymous with and/or equivalentto “communications channel,” “data communications channel,”“transmission channel,” “data transmission channel,” “access channel,”“data access channel,” “link,” “data link,” “carrier,” “radiofrequencycarrier,” and/or any other like term denoting a pathway or mediumthrough which data is communicated. Additionally, the term “link” asused herein refers to a connection between two devices through a RAT forthe purpose of transmitting and receiving information.

The terms “instantiate,” “instantiation,” and the like as used hereinrefers to the creation of an instance. An “instance” also refers to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code.

The terms “coupled,” “communicatively coupled,” along with derivativesthereof are used herein. The term “coupled” may mean two or moreelements are in direct physical or electrical contact with one another,may mean that two or more elements indirectly contact each other butstill cooperate or interact with each other, and/or may mean that one ormore other elements are coupled or connected between the elements thatare said to be coupled with each other. The term “directly coupled” maymean that two or more elements are in direct contact with one another.The term “communicatively coupled” may mean that two or more elementsmay be in contact with one another by a means of communication includingthrough a wire or other interconnect connection, through a wirelesscommunication channel or ink, and/or the like.

The term “information element” refers to a structural element containingone or more fields. The term “field” refers to individual contents of aninformation element, or a data element that contains content.

The term “SMTC” refers to an SSB-based measurement timing configurationconfigured by SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS/PBCH block.

The term “a “Primary Cell” refers to the MCG cell, operating on theprimary frequency, in which the UE either performs the initialconnection establishment procedure or initiates the connectionre-establishment procedure.

The term “Primary SCG Cell” refers to the SCG cell in which the UEperforms random access when performing the Reconfiguration with Syncprocedure for DC operation.

The term “Secondary Cell” refers to a cell providing additional radioresources on top of a Special Cell for a UE configured with CA.

The term “Secondary Cell Group” refers to the subset of serving cellscomprising the PSCell and zero or more secondary cells for a UEconfigured with DC.

The term “Serving Cell” refers to the primary cell for a UE inRRC_CONNECTED not configured with CA/DC there is only one serving cellcomprising of the primary cell.

The term “serving cell” or “serving cells” refers to the set of cellscomprising the Special Cell(s) and all secondary cells for a UE inRRC_CONNECTED configured with CAL

The term “Special Cell” refers to the PCell of the MCG or the PSCell ofthe SCG for DC operation; otherwise, the term “Special Cell” refers tothe Peell.

1. A first access node for implementing a cross-link interference (CLI)information exchange procedure in a wireless communication system, thefirst access node comprising: radio front end circuitry configured toreceive a cross-link interference CLI request signal from a secondaccess node; and processor circuitry configured to generate a CLIresponse signal including time-division duplex (TDD) configurationinformation, wherein the radio front end circuitry is further configuredto transmit the CLI response signal to the second access node.
 2. Thefirst access node of claim 1, wherein the TDD configuration informationcomprises: a list of TDD configurations.
 3. The first access node ofclaim 2, wherein the list of TDD configurations comprises: a cellidentifier (ID); or a common TDD configuration.
 4. The first access nodeof claim 2, wherein the list of TDD configurations comprises: a cellidentifier (ID); and a common TDD configuration.
 5. The first accessnode of claim 1, wherein the TDD configuration information comprises: alist of dedicated TDD configurations.
 6. The first access node of claim5, wherein the list of dedicated TDD configurations comprises: adedicated TDD configuration; or a user equipment (UE) identifier (ID).7. The first access node of claim 1, wherein the TDD configurationinformation comprises: a list of user equipment (UE) CLI referencesignal (RS) transmission configurations.
 8. The first access node ofclaim 7, wherein the list of UE CLIRS transmission configurationscomprises: a UE CLI RS transmission configuration; or a UE identifier(ID).
 9. The first access node of claim 1, wherein the radio front endcircuitry is configured to receive the CLI request signal and totransmit the CLI response signal over an Xn interface or a F1 interface.10. A first access node for implementing a cross-link interference (CLI)information exchange procedure in a wireless communication system, thefirst access node comprising: processor circuitry configured to generatea CLI request signal; and radio front end circuitry configured to:transmit the CLI request signal to a second access node; and receive aCLI response signal from the second access node, the CLI response signalincluding time-division duplex (TDD) configuration information.
 11. Thefirst access node of claim 10, wherein the TDD configuration informationcomprises: a list of time-division duplex (TDD) configurations.
 12. Thefirst access node of claim 11, wherein the list of TDD configurationscomprises: a cell identifier (ID); or a common TDD configuration. 13.The first access node of claim 10, wherein the TDD configurationinformation comprises: a list of dedicated TDD configurations.
 14. Thefirst access node of claim 13, wherein the list of dedicated TDDconfigurations comprises: a dedicated TDD configuration; or a userequipment (UE) identifier (ID).
 15. The first access node of claim 10,wherein the TDD configuration information comprises: a list of userequipment (UE) CLI reference signal (RS) transmission configurations.16. The first access node of claim 15, wherein the list of UE CLIRStransmission configurations comprises: a user equipment (UE) CLI RStransmission configuration; or a UE identifier (ID).
 17. The firstaccess node of claim 15, wherein the radio front end circuitry isconfigured to transmit the CLI request signal and to receive the CLIresponse signal over an Xn interface or a F1 interface.
 18. A system forimplementing a cross-link interference (CLI) information exchangeprocedure in a wireless communication system, the system comprising: afirst access node configured to generate a CLI request signal; and asecond access node configured to: receive the CLI request signal fromthe first access node, and generate a CLI response signal includingtime-division duplex (TDD) configuration information, wherein the firstaccess node is further configured to receive the CLI response signalfrom the second access node.
 19. The system of claim 18, wherein the TDDconfiguration information comprises: a list of TDD configurations; alist of dedicated TDD configurations; or a list of user equipment (UE)CLI reference signal (RS) transmission configurations.
 20. The system ofclaim 18, wherein the first access node is configured to receive the CLIresponse signal and the second access node is configured to receive theCLI request signal over an Xn interface or a F1 interface.